Installation From Scratch – Workflow
Version 6.1 (In Development)
Overview
The following is intended for System Administrators and Business Analysts to set-up the OpenForms 6.1 Workflow Management Module.
101-wm-install-from-scratch
Version 6.1 (In Development)
The following is intended for System Administrators and Business Analysts to set-up the OpenForms 6.1 Workflow Management Module.
101-wm-install-from-scratch
Version 6.1 (In Development)
This page is intended for System Administrators, Business Analysts and Technical Service.
WARNING: Only Govern Technical Services should use this query. Handle with Caution. |
Click to see the link to download a ZIP file of the SQL query CREATE QUERIES for WM LINKS.sql
101-wm-install-queries-linktypes-sql
Version 6.1 (In Development)
This page is intended for System Administrators, Business Analysts and Technical Service.
The following queries are used when installing or configuring the Workflow Management module.
wmGetLinkType (system)
wmGetLkTypes (system)
wmGetLkTypesNA (system)
N/A
Click here for an example of a MSSQL Query that creates queries and items to use for Link Types
naNameAddr – Get Name & Address (system)
wmGetLinkType (system)
wmGetLkTypes (system)
wmGetLkTypesNA (system)
101-wm-install-queries-linktypes
Version 6.1
If you need to create multiple workflows, you can facilitate the process by automating it. You can set up the automatic generation of workflows from an action or from a batch process.
You can use the same principal to automate the creation of a single workflow if this is required at a specific step in an existing workflow process. For example, once a building permit is approved, you could add a step with an action to generate an electrical permit automatically.
Workflows can be launched automatically from any of the following:
TIP: If you need to link the automatically generated workflow(s) to an existing workflow, it is easiest to set this up from an action. There is no automatic link from the batch process. |
For details, see
http://kb.harrisgovern.com/101-wm-bp-010
103-wm-parm-Action14-CreateWorkflow
Version 6.1 (In Development)
This page is intended for System Administrators and Business Analysts to create a Workflow form and configure the form controllers.
The activities are a list of actions and validations contained in a bunch of steps which are performed in some order depending on the responses given its activities.
So each activity and step process some actions for a workflow.
Activities can be Initiated and after that completed by giving a response result for the completed action.
The following is the configuration of the main activity custom control object properties.In addition, since multimedia can be embedded in workflow, setup will be required.
There are 2 OFD properties (MultimediaWindowHeight and MultimediaWindowWidth) to control the Size of the Multimedia Window.
When in Govern, by clicking on the Multimedia Hyperlink in the Activity Panel or by Double Clicking on the small Multimedia picture in the Tree View this will open the Multimedia control to manage the linked multimedia documents of the selected activity.
First you need to drag the Custom Entity control object to the form header then click on the tab header to set the properties.
Element | Property | Setup |
---|---|---|
Misc. | Action | WM_ACTIVITYSTATUSHIERARCHY_CONTROL |
Name | n/a – Maintain by System | |
Parent Entity | The form Root Entity | |
Is Visible | n/a | |
Name | Maintain by System | |
Properties | ||
Misc. | MultimediaWindowHeight | To control the size of the Multimedia Window Suggested size = |
MultimediaWindowWidth | To control the size of the Multimedia Window Suggested size = |
|
Tab Sequence | Tab Stop Sequence Number | Standard OpenForms |
Text | ||
Misc | En | Enter the name that will be displayed for the form entity i.e Activity |
Internal | Element | Instructions |
Not applicable |
The following security options are available for the controller
101-wm-install-wm_activity_status
Version 6.1 (In Development)
This is an action trigger intended for use with the Govern Workflow. This action trigger will allow a user to execute an external command in a workflow process. Typically the command may be to open a web page, execute a windows application, or to execute an installed application.
The parameters for this Action are as follows…
Trigger – This is the status point at which the action is triggered, e.g. At Initialization, All Status, and so on; this field is not modifiable at this point.
Action – This is the list of available actions that are available to be configured; select Invoke an External Command.
When the Invoke an External Command action is selected, the following option(s) are displayed:
External Command – Select the form that
NOTE: Actions that are added to the ‘On Request’ section in the Options group will have a Label parameter to name the link that will invoke the action. Any actions that are executed On Request require a link. |
As this is a standard action that is used in the context of a Workflow, it is configured through the Govern New Administration (GNA).
External commands are defined in the GNA External Command Editor.
Create a new command through the External Command Editor.
To configure the action in the GNA…
Refer to the External Command Editor documentation (103-ED-007) for full details about configuring an external command. External commands may include, but are not restricted to, executing a Windows application, a Govern application, or launching a web page.
After configuring the external command, ensure that it appears on the list of external commands on the left hand side of the editor form.
To configure the action in the GNA…
At Initialization – All actions that are configured in this section are automatically executed at the initialization of this step. When there are two or more actions, the order of initialization may be changed with a click and drag action.
All Status – The actions that are configured in this section are automatically executed after the completion of any available statuses, e.g. Initialization, Completion, and so on.
On Request – See On Request Actions below.
(Available Release 6.1.1702)
Typically an action is called automatically on Initiation or on Completion, actions may also be added to the On Request section. The actions in this section are executed manually; i.e. users will have to click on the button link that will trigger the action.
To add the Action in the Steps form…
Label – On the Add a new action form there is a mandatory 25 character alphanumeric label that is used for the action link. Completion of the Label parameter is mandatory; this will be the name of the link that will invoke the action.
When correctly configured, the actions will be executed based upon their configuration in the GNA.
The Invoke an External Command action will execute the application. For example if the Windows Calculator application was configured, it will be launched with the focus being on the application; it may be necessary to click back on the Govern application to see it.
Triggers that were configured to be executed as “On Request” will be presented as links on the right hand side (RHS) Available Actions group under the Activity tab. These links will be presented in the Available Actions group, in the order that the actions were entered. Available Actions that correspond to each step can be viewed with a click on the step; they will be presented in the group. With the group, to change the order, they will need to be rearranged in the options group, saved, and refreshed in the GNA.
The following table(s) were implicated in the implementation of this feature:
To view available Workflow Actions, click here for the complete Workflow Actions list.
103-wm-parm-Action21-InvokeExternalCommand
Version 6.1 (In Development)
This controller is used for a Workflow Open Form with a category that ‘Allow additional types’. It must be set for the secondary entity, to manage the additional types.
When the Open Form is initialized, for the entity that manages the types:
NOTE: This page is intended for System Administrators and Business Analysts to create a Workflow form and configure the form controllers. |
The following is the configuration of the controller or custom control object properties.
To configure, you need to select the CATEGORY and TYPE entity from the list of entities and drag it to the form header.
Than click on the tab header to configure.
Element | Property | Setup |
---|---|---|
Browse | Columns | Select the columns for the browse and the order to appear on the field |
Hidden on Load | If hidden on load, user will need to click on the browse button | |
Show on Left | If not clicked will show on top | |
Size | Space to use when the browse window is used. TIP: Reduce size during the configuration in order to have more room to see the form itself. |
|
Controller | Controller | WM_ADDITIONAL_TYPE_CONTROLLER |
Controller Properties | n/a | |
Miscellaneous | Allow Delete (optional) | Allow delete of a workflow record (Standard OpenForms Option Available) |
Allow Insert | Allow creation | |
Allow Save | Allow save | |
Configuration | Filter by system id | n/a |
Filter by constants | n/a | |
Order by | n/a | |
Reposition | n/a | |
ID Setters | n/a | |
Record Description | Expression | For example: |
Expression option | Convert Null parameters to default Value must be set to TRUE? | |
Tab Sequence | Number | OpenForms standards |
Text/Misc. | Text | Used for the business entity name? |
Misc EN | Will be used for the SY DICT description? | |
Misc FR | ||
Internal | Element | Controlled Internally as READ ONLY |
Attribute | The controller takes care of the following attributes so that they are read only. WM_ID, TYPE_CODE, IS_MASTER, LAST_MODIF_UID, LAST_MODIF_DATE |
|
Other | n/a |
101-wm-install-wm_addtional_type_controller