Sending query results as a CSV email attachment
Background
Workflow Strings are a mechanism introduced in early version 5.x that separates the text in Workflow notifications from the Workflow parameter itself. They were added to Activate to allow editing of the email messages via the web portal independent of the workflow and also facilitate multi-lingual notifications.
The message text is stored in a Language Resource parameter named “LanguageCode-Strings” in the Task with the workflow that uses it, where “LanguageCode” is a two letter ISO language classification code (https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), e.g. en-strings for an English language message. These parameters are created automatically when a workflow notification message is edited.
Any Workflow notification that is referencing a Workflow Strings parameter will show the Message subject next to the notification in bold blue text:
Using Workflow Strings
Not Using Workflow Strings
Stopping Activate Administrator from Creating Workflow Strings
As of version 7.1.0 the use of Workflow Strings is no longer a per-user setting; changes made apply to all users. The use of Workflow Strings can be controlled both by a DefaultEnableWorkflowStrings parameter and by toggling the setting within the Workflow.
This allows Workflow Strings to be:
- Disabled Globally Set a DefaultEnableWorkflowStrings in the root of Tasks and configure workflows to use the newly defined Example; 1.a. in “Use a DefaultEnableWorkflowStrings parameter” below
- Disabled per Task Set a DefaultEnableWorkflowStrings in the Task itself Example; 1.b. in “Use a DefaultEnableWorkflowStrings parameter” below
- Overridden within a Workflow. Example; “Override the default setting within a workflow” below
For the behaviour in versions prior to 7.1.0 see Workflow Strings - for Versions Prior to 7.1.0
Existing Workflow Strings:
When no Workflow Strings language resource parameter exists, the Workflow honours the setting defined by creating a DefaultEnableWorkflowStrings parameter.
When a Workflow Strings language resource parameter exists it will be used by its associated workflow and the Use Workflow Strings property in the workflow will show as True. The Workflow has to be manually set to use the default defined by a DefaultEnableWorkflowStrings parameter and stop using Workflow Strings.
When a Workflow is edited and set to not use Workflow Strings, Activate Administrator will ask if any existing Workflow Strings associated with the Workflow should be merged back into the Workflow. Examples; 3 in “Use a DefaultEnableWorkflowStrings parameter” and 2 in “Override the Default Setting Within a Workflow” below. Based on the choice made:
- Yes The Workflow strings will be merged back into the workflow. The language resource parameter will be renamed with an underscore prefix to disable it
- No The language resource parameter will be renamed with an underscore prefix to disable it
- Cancel No changes will be made and the Workflow will continue to use Workflow Strings
For the behaviour in versions prior to 7.1.0 see Workflow Strings - for Versions Prior to 7.1.0
Steps to Disable Workflow Strings
Either:
Use a DefaultEnableWorkflowStrings parameter
Create a DefaultEnableWorkflowStrings parameter at the level where the change should apply. eg.:
For all Tasks, at the root of Tasks
For a specific Task, within the Task
Edit any Workflows that are using Workflow Strings, i.e. have a Workflow Strings language resource parameter, and set the “Use WorkFlow Strings property to False
Choose to merge any existing Workflow Strings into the Workflow
Or
Override the Default Setting Within a Workflow
Change the Use Workflow Strings Property to False
Choose to merge any existing Workflow Strings into the Workflow