Workflow Documentation

Great! so you have learnt to build a form on the Low Code platform else click here, congrats now we will move towards building process work flow
Draw Your Business Flow :-
How does this work?

Drag and drop the states connect the nodes with Activities, define the roles for respective activity and your business flow is almost ready, (confused? Don’t be, let us read more below its simple)

  • How to create a workflow on the Amplelogic Low Code Platform?

    Navigate to the workflow option on the top which would be appearing on the top(color code to show you the pending task) remember the form has to be built before this step.

  • By clicking on the Workflow tab, the user will be redirected to the Workflow page.
  • After clicking on add button one popup window will appear by asking the Workflow name and to select the form against which the workflow is being created.
  • In name field the user should write the work flow name as per requirement & in select form field, all created form names will be appeared in drop down. Ensure that the naming convention for the process flow is similar to the form to avoid confusion.
  • Select form name from drop down and click on next, the user will enter into the workflow design page, wherein the below mentioned buttons will appear
    Drag State
    Edit
    Translation
    Save
    Copy
    De Active
    Print

States :-

State is something unique to Amplelogic Low Code platform which can be explained as nodes or current check-point of the form from where it has a next destination in the process flow, which needs to be connected with the Activities.

Hover the mouse on “Drag State” and drag the state in the desired position in the page.
One popup window will appear wherein the state properties will be displayed Tab wise

Details
Field Map
Dependencies
E-Mail I’d
Others
Dynamic Task Grid-Properties

Details :-

Whenever the user will drag one state one popup will be displayed by highlighting the Details tab. In this detail tab few necessary details of the state need to be entered. Like Name (Name of the state), Description, Highlight Tab, Initial State, Last State.


Name : The given name will be considered as the name of the state. The state names can be duplicate in a single workflow. Without giving the state name the state can’t be saved.

Highlight Tab : This is a dropdown wherein all the Tabs present in the respective form will get displayed. If any tab is selected here in this then after opening any record (in run time) in that state that selected tab will be displayed by default.

Description : The description field is present to maintain any description of the state, if required.

Initial State : By checking this the designed will define that the workflow will begin from that particular state.

Things to keep in mind : In run time after clicking on Add button in the form page the user will be redirected to the state wherein the Initial state has been marked as enabled. In a single workflow multiple initial states can’t be configured.

Last State: By enabling this button the designer will define that this state is the last state for the workflow.

Things to keep in mind : In a single state the user can’t check both “Initial State” & “Last State”. If any state is checked as last state that means, there if any record exists that wouldn’t appear in pending dashboard (in run time) and in audit trail of that record it wouldn’t display where the record is pending which red dot.

Based on the properties of the state you have defined, the flow chart automatically takes it shape, for eg: the initial state is represented in circle and if you have defined conditions in the state it will take the shape of a decision box with conditional workflows.


Field map :-

In this tab the user will be able to configure the visibility of Tabs, Sections and Fields present in the respective form. Herein this Visible, Content Check & View History columns will be displayed for configuration against each field.
In design time if any Tab/Section/Field is checked as Visible that means in run time at that state (if any activity is not visible in that state.)
In design time if any Field is checked as Content Check that means in run time at that state if any value is not therein inside the field then the field will not be visible.
In design time if any Section is checked as Content Check that means in run time at that state if any field is not visible in that state then the section also will not be displayed.

View History : If any field is marked as view history then in run time if any previous value exists for that field that will be displayed by clicking on the view history icon. It will be helpful for the user to know the value of a field if it has been edited for multiple times.

Rule Engines:- The critical part of any software development process is being clear on the requirements but ideally no requirement is perfect in the initial go which leads to a lot of time waste and rework as change requests keep coming, Amplelogic low code platform provides a visually appealing and easy rule engine tab for you where the administrator of the application can create as many rules on the go.

Finance rules:- Monetary transactions
Quality Control
Manufacturing
Quality metrics
Production, operations etc.
execute your own rules with the visual rule engine the same is explained in detail below

Dependencies(States) :-

By the name dependency, we can figure out that the functionality is used to set dependency among the workflows.

In dependency the user will be able to see the below mentioned fields, along with “Add Dependency” button.

Dependency Type
Target Activity
Workflow
Target State
Message
Manual
All Source
Allow Next Level Activities

Dependency Type : In dependency type field the user will be able to see two values “Parent” & “Child”. In the parent workflow if the user wants to set a dependency upon a child workflow in that case the user shall have to select dependency type as “Child”. Similarly, in the child workflow if the user wants to set a dependency upon a parent workflow in that case the user shall have to select dependency type as “Parent”.

Target Activity : By defining the value in this field the user will define on which activity the dependency will work.
Suppose the requirement is to show the “Send to HR” activity only if the child record/records reach to a defined state. In that case we shall have to select “Send to HR” activity in the Target Activity field. The activities which all have been initiated from the state (wherein we will configure dependency) those only will appear for selection in Target Activity state.


Work Flow-Dependency : Here in this field all the workflows present in the application will get displayed. By selecting any of these the designer will define the workflow, on which the selected activity (selected in target activity) is dependent upon.

Target State : In this field all the states present in the selected workflow (selected in workflow field) will get displayed. The designer will be able to select multiple states by holding control button. If two states are against one dependency, then it will be considered as “Or” condition which means if the dependent record reaches to any of those states then the condition will get satisfied. Whatever state will be defined, until and unless the records or any of the record (dependent upon “All Source” configuration) reaches to the defined state the selected will not get displayed/ will not be auto performed (depending upon whether “Manual” is enabled or disabled)

Message : Whatever will be given here in this field, that text will get displayed to the end user at that state whenever the dependency will be active on that state.

Manual : If the user enables “Manual” in that case the selected activity (selected in Target Activity) will be displayed to the user, once the dependency condition is satisfied. If the manual field is displayed in that case the selected activity will be auto executed by the system once after the dependency condition is satisfied.

All Source : If the designer enables this button then in run time whenever all the generated child records reach to the target state then only the condition of dependency will get satisfied. If All Source is not checked then if among the generated dependent records if any one reached to the target state, then only the condition will get satisfied.

Allow Next Level Activities : If the user enables this field, that means in run time if once the condition is satisfied, throughout the flow the condition will get satisfied for that record. If this field is checked then every time in run time the system will check the condition.

Note : The user will be able to add multiple conditions in one state.

Alerts & Reminder :-

This functionality is used to remind the user/users (where any activity is pending for their action) about the pending record.

Configuration Required :-

To configure this the user shall have to do necessary configurations present in the Reminder tab of Workflow->State.


In the Reminder Tab configuration of two functionalities can be done, Reminder & Escalation and without configuring reminder, escalation can’t be configured. In the rest of the points, the explanation of Reminder functionality has been provided.

At the top row in Reminder Type section there are two option, Default & Target Date Based


If the user selects the Target Date Based option then one more field will appear below, named “Select Target Date” field, wherein all the Date picker controls which are present in the form of the respective workflow will appear for selection. On the other hand, the “Idle Time” field will disappear on selection of “Target Date Based” value.


Significance of “Target Date Based” field in the reminder configuration : If the user adds the Reminder by considering the Target Date Based field then the reminder will work on the present date value of the control, selected in “Target Date Based” option.

Significance of “Default” field in the reminder configuration : If the user selects Default option at the time of configuring the reminder then the record submission date/time at that state (wherein the reminder is being configured) will be taken into consideration.

In Condition if we select “Field Based” value then the below mentioned fields will appear, newly.
a. Select Field
b .Master Data (Visible Only)
c. Field Value


In “Select Field” dropdown all the fields which are present in the respective form and having master data, will appear for selection. Once after selecting the field the liked Master Data name will appear in the “Master Data” field & in “Field Value” field all the master values present in displayed master data (displayed in Master Data field) will appear for selection, from where the user will be able to select only one value.


Significance of “Field Based” field in the reminder configuration : If the configured condition is satisfied then only the reminder & escalation mails will be triggered, if not then those will not get triggered.

Calendar Days : If this field enabled then the reminder mails will consider the consider the calendar days. In admin level calendar there is a provision to define holidays and week offs in that case those days will not be considered as a working day.

Duration Type : In duration type the designer will get two options to configure Days & Hours. To determine the unit of the given value this field is provided. If selected value is Days then mails will be triggered considering days, if it’s hours then it will take hours into consideration.

Reminder Name : This field is used just to define a name of the configured reminder. It wouldn’t be displayed anywhere in runtime to the user.

Idle Time : This field is used to define how much time it will remain idle from the Record Submission time or from the selected date (as per the configuration)

Remind Every : This field is used to define; the reminder mails will be triggered within how much period of interval. If we set it as 1 day, then every day the reminder mail will be triggered.

Start Time before Ideal Time : Whatever value will be entered herein; the first mail will be triggered on (Ideal Time – Start Time before Idle Time) days/hours before the record submission date or the selected date.

Escalation

If we click on “+” icon against the Escalation, then the below mentioned fields will appear. Hierarchy Level, Remind Every, Start Time after Idle Time.

Hierarchy Level : Herein this field the designer will be able to select levels like 1,2,3 and so on. The level will be picked from the people hierarchy (as per the mapped supervisor level). The escalation mail will be sent to the selected level of supervisor of the person where the record is pending.

Remind Every : This functionality is same as the field present in reminder section. After triggering the first escalation mail depending upon this field it will be dependent that for how much interval the

Start Time after Idle Time : Whatever value will be provided herein the first escalation will be triggered after that many days/hours from the Default Date or Selected Date.

Email id's :-

This functionality is used for sending mail in run time based on role if Runtime Email is checked.

If Runtime Email Audit is checked then the audit of sent emails will be displayed in run time for the selected Role users in that state.



Note : If we configure Runtime Email property in a state from where no further activity is present, then in that case the Compose Email icon will not appear to the end user.

Active Inactive Records :-

If the designer configures this functionality by enabling the “Active Inactive Records” field in any state then the users mapped in the roles, which are having the permission to activate or inactivate record, they will get the option to Activate or Inactivate the records of that form (the form for which permission has been provided to the role).

In run time the inactivated records will be displayed if we disable Inactivate Records field in search page and search for records. Once after editing the inactivated record the user will get the option to Activate the record again.





Enable Change Request

This option is used to send back any record to previous state. IF the designer checks this option then all the states present in the previous flow of that state will get displayed for selection that can be selected. Multiple states can be selected by holding the Crtl button in keyboard. If multiple states are selected then in run time the user will have the option to send the record to those States.

Note : To display this option to the users in run time the role should have the Enable Change Request option in design time. If there is no further state then this functionality will not work.




Control display of activity

Click on control display activity the following pop up will display as mention below.


Here based on the requirement user has to select the filed from drop down, select master data and need to set the activity based on state condition and need to click Add to container and save changes.
For Example: There is a selection of Categories (Radio button) like Food, Textiles, Electronics when the user selects the Food he will get only Food menu for Selection or if he selects the Textiles he gets only textiles menu for the selection.

Show Records in Calendar

In any state if the designer enables this functionality and therein that state if any reminder is added depending upon the target date. Then that record will be displayed in the selected date cell of the calendar tab. To get this functionality in application level we need to enable the calendar.

Show Records in Calendar :-

This property is used to define from where the traveller record of dynamic task grid should be cloned. Herein this section all the dynamic task grids present in the application will get displayed for selection.


Dragging One Activity :-

Map/ Link the activity from one state to another the following pop up will be appeared as mention below


Details :-

In the following interface, we should write the activity name, that will be displayed to the user while performing the activity.

If we have more number of tabs in form and want to display the following tab automatically to the user while editing / Adding the record then respective tab need to select in highlighted tab

Description: Here we can write the description of the activity.

Ack. Message: this we use when we want to display the message to the user once the activity is completed.

Cong. Message: this we use when we want to display the message to the user before the activity is completed for confirmation.

E- Signature: this functionality we use in run time if we select the check box then in run time whenever we are submitting the activity, one pop-up will display for password. After filling the password only, we can submit the activity.

Do Not Allow to User: If we don’t want to display the activity to the user then we used.

Is active: Is active is used when we want to active the activity till the end of the application.

Field Map :-

Click on field map the following interface shall be appeared as mention below.


Here we must give the visibility permission to the user for fields and need to provide which field should mandatory and non-mandatory.

Content Check: if it is checked and user has not filled/feed data in respective field and perform the activity then in next activity content check permission field will not display.

View History: is used to see the date and time for the activity.

Email view mobile view: is used to see the email notification when the activity has done.

Action :-

Click on Action tab, the following page shall be appeared as mention below.


The following Add action shall be appeared in drop down as mention :

Generate Reference Number :-

The Purpose of this action is to generate a unique number to a record in run time.

Select the Generate Reference Number Action in the Add Actions Drop-down the following screen reflects as shown below. To generate the reference number there should be one defined format of reference number in form level.


We can override the reference number format that is given in the form level by clicking on the Override button, we can provide a new format here in the fields that are shown below


After giving the Reference number format click on submit button and the action is saved as shown below.


The reference number will reflect at the run time after the activity, that has action in it.

InActivate Record :-

The purpose of this action is to in-Activate a record after an activity performed

Select the In-Activate Record action in the Add Action Drop-down


After Selecting the In-Activate Record click on submit button and the action is saved as shown below.


By giving the Action In-Activate Record ,record will be In-Activated after this Activity.

Assign to User :-

The Purpose of this action is to assign an activity to the particular person who was responsible for that activity

Select the Assign user Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


We must select the Assign user control in Assign user field as shown below.


Click on the Acceptance Control and select the Fields that need to be used in the run time by using it only the record will be assigned to selected user as shown below.


Select the values that are available in the Acceptance control value that are regarding to the selected field in Acceptance Control as shown below.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Assign to Multi User :-

The Purpose of this action is to assign a activity to the Multiple persons who were responsible for that activity

Select the Assign to Multi user Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


We have to select the Multi Assign user control in Multi Assign user field as shown below.


Click on the Acceptance Control and select the Fields that need to be used in the run time by using it only the record will be assigned to selected user as shown below.


Select the values that are available in the Acceptance control value that are regarding to the selected field in Acceptance Control as shown below.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Assign Department :-

The Purpose of this action is to assign a particular activity to the particular Department.

Select the Assign to Department Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


We must select the Department control in Assign Department field as shown below.


Click on the Acceptance Control and select the Fields that need to be used in the run time by using it only the record will be assigned to selected user as shown below.


Select the values that are available in the Acceptance control value that are regarding to the selected field in Acceptance Control as shown below.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Assign Division :-

The Purpose of this action is to assign a activity to the particular Division

Select the Assign to Division Action in the Add Action Drop Down, the Following screen will be reflected as shown in below.


We must select the Department control in Assign Division field as shown below.


Click on the Acceptance Control and select the Fields that need to be used in the run time by using it only the record will be assigned to selected user as shown below.


Select the values that are available in the Acceptance control value that are regarding to the selected field in Acceptance Control as shown below.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Assign to Initiator :-

The Purpose of this action is to assign the record back to the initiator who initiates the record.

Select the Assign to Initiator Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Assign to Self :-

The Purpose of this action is to assign the record to self.

Select the Assign to Self Action in the Add Action Drop Down, the Following screen will be reflected as shown in below.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Supervisor Approval :-

The Purpose of this action is to send an approval activity to the record initiator’s supervisor.

Select the Supervisor Approval Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Employee Hierarchy Approval :-

Select Employee hierarchy drop down, the following page shall be appeared as shown below


Default State : This state will auto execute when no user available in Approval Hierarchy.

Organization hierarchy Dependency : If it is checked then system will follow same user department from Approval hierarchy user. Otherwise it will not check department for approval hierarchy

Source Hierarchy : System shall display all created in hierarchy record in drop down for Source Hierarchy.

Approval Hierarchy : System shall display all created in hierarchy record in drop down for Source Hierarchy.

Email Notification :-

It will notify the next level work flow role user where ever it is pending.

Note: If in same activity another action is saved like “Assign department or Assign Division” then condition will be applied and mail will be trigger to the only department user or division user of next level work flow role.

Save Activity Stamp :-

The Purpose of this action is to track the record initiator name, date and time of creation.

Select the Save Activity Stamp Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


Select the Time Stamp in the Select Time Stamp Field as shown below


Type any text that need to display with the date and time in the Display Text field as shown below


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Generate Barcode :-

The Purpose of this action is to generate a barcode to the record.

Select the Generate Barcode Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


Select the Barcode control in the Barcode Field as shown below


Select the Barcode type to generate in the record in Select Generation Type Drop down.


If Acceptance control is selected in the Select Generation Type dropdown a new dropdown is visible to select the calculator fields based on the calculations in that field bar code is generated


If Generate Random String is selected in the Select Generation Type dropdown, a random barcode strings are generated.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Copy Inline Grid :-

The Purpose of this action is to copy data from one inline grid to another inline grid of same form

Select the Copy Inline Grid Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


Select the Source Inline grid in the Source Grid Dropdown.


Select the target in line grid in the Target Grid Dropdown.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Copy Grid View :-

The Purpose of this action is to copy data from one grid to another grid of same form

One dummy activity is required in the workflow for copying the information in the respective form.

Select the Copy Grid View Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


Select the source grid view control in Source Grid drop down and Target grid view control in Target Grid dropdown as shown below


After selecting the Source and target grid click on Confirm grids


By clicking on change grids, we can change the source and target grid fields


We can select the target state from where the data need to be copied from source grid to target grid.


need to select the Source Column and target column as shown below.


After selecting the Source and target columns they should be added by clicking on add to container individually as shown below.


We can also delete the columns added by clicking on ‘X’ as shown above.

By clicking on the Over-ride data button, we can override the copied data.

Note : Columns names should be same while adding to the container.

After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Copy Data from External Form :-

The Purpose of this action is to copy data from one form to another form.

Select the Copy Data from External Form Action in the Add Action Drop Down, the Following screen will be reflected as shown in below


Select the Source from that need to be copy the data in Source Form Field as shown below


After selecting the source form click on Confirm source form button as shown below


Source Form can be changed by clicking on change source form button as shown above

After selecting the Source form Source field and Target Filed should be selected to copy the data.

Note : Source field name and target field name should be same.

After selecting the Source and target fields click on Add to container button


We can also delete the Source and target fields added by clicking on ‘X’ as shown above.

After adding to the container, we should select the Source Dependent Field and Target Dependent field.


Note: the field name and values of Source dependent field and target field should be same.

We can select the Source dependent state of Source form at which state data should be copied as shown below.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Task Generation :-

The Purpose of this action is to generate a Task to the user/Department/multiple users.

There must me one state before the state, wherein the task is being generated.

Select the Task generation Action in the Add Actions Drop-down the following screen reflects as shown below


Select a task grid control such as Task grid, Department task grid, Multi user selector in Target Task grid dropdown.


Select the Out state where the task should be generated in the Out-state Dropdown.


Click on the Acceptance Control and select the Fields that need to be used in the run time by using it only the record will be assigned to selected user as shown below.


Select the values that are available in the Acceptance control value that are regarding to the selected field in Acceptance Control as shown below.


Multiple values can be selected in the Acceptance Control Value

Data can be Over-ridden by clicking on the Override button.

After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Calculated Field Action :-

The Purpose of this action is to Calculate the arithmetic operations between the fields

Select the Calculator Field Action in the Add Actions Drop-down the following screen reflects as shown below


Select the Calculator field in the Calculation On Dropdown as shown below.


After Selecting the Calculator field Formula should be selected in the Formulas Dropdown where they are initiated from Formula parser.


After selecting the above options click on submit button, it will be added to the actions grid as shown below.


Condition :-

Click on Condition tab, the following interface shall be appeared as mention below.


Here we can set the condition by selecting the field, operator, Field type, Execute activity.

In run time whenever the condition satisfied, automatically condition activity will be performed.
Example : Suppose in form, I have one Name field (Text box) and one country field (Drop down). (Country Name: India, Pakistan). My requirement is, when I select Country as India and Perform Submit activity, System should automatically perform Approved Activity. Else if selected country as Pakistan then auto perform reject activity after submitting Submit activity.



Roles :-

It is used to define the role for selected activity. By default, system will display all created role in role tab as mention in screen shot.


Customization :-

Click on customization tab, the following interface shall be appeared as mention below.


To Validate section: We use Procedure name for Validation purpose.

Fields : System shall display all field name in field section. Based on the selected field, system shall pass the details to the data base and display the validation message define in Procedure during run time.

After Execution section : We use Procedure name for customization purpose. During run time it’s work as per logic build in Procedure.

Edit we used if we want to change the work flow name in future.


We use copy if we want to clone same work flow and form.

Click on copy the following pop up box shall be appeared as mention below.


Here we should click on yes, the new pop up shall be appeared as mention below


Here we should give the form name and work flow name and need to save, the same work flow and form will be created, and it will display in the list as mention below


Here user can see the name of work flow, how many states, activity we have used for work flow and many more like who created, when created and current version.

We use this when we don’t want this work flow to be active/RUN in my application.

It is used to print the work flow.