AutomationEdge Core Entries

AutomationEdge Core Entries



AutomationEdge Core Entries

Debug Log

Description

The Debug Log process entry is used for logging Process/Workflow variables and fields into AutomationEdge Agent log (agent.log) file when Process/Workflow is run from AutomationEdge; or in Process Studio log (process-studio.log) file when Process/Workflow is run from Process Studio.

Configurations

No.

Field Name

Description

1

Step Name

Specify a unique name for the process entry on the workspace area. A process entry can be placed on the canvas several times; and each instance of the entry must have a unique name. 

2

Log Level 

Select a value from the drop down list. Possible values are DEBUG, INFO, WARN, ERROR in ascending order of severity.

The debug log step will collect logs at the level selected here or at higher lever of severity.

However the base level is governed by the Agent Logger setting (DEBUG, INFO, WARN or ERROR) in the log4j2.xml file available in the agents conf folder. All logs at a higher level than this setting will be visible in Agent log file.

In case of Process Studio the base level is governed by the ProcessStudioLogger setting (DEBUG, INFO, WARN or ERROR) in the log4j2.xml file available in the Process Studio distribution conf folder. All logs at a higher level than this setting will be visible in Process Studio Log file.


Variables Tab

No.

Field Name

Description

1

variables

Accepts comma separated list of variables to be logged in.


Fields Tab: Contains table to accept fields to be logged in.

No.

Field Name

Description

1

Name

Name of field to be logged in.

2

Type

Auto populated once the field name is selected. It is not editable.


Notes: Secret variables are logged as ‘XXXX’

Agent logs are also accessible from AutomationEdge Agent Log menu. Debug logs are part of Agent Logs. Agent Logs are visible by navigating to the Logs menu and Agent Logs sub-menu in AutomationEdge. Agent logs can be obtained by clicking the New Request Button on the top right corner.  Source should be chosen at Agent or Workflow level as shown in the screenshot below.



Send Email

Description

Send email process entry can be used in a process to send emails.

Configurations

No.

Field Name

Description

1

Process Entry Name

Specify a unique name for the process entry on the workspace area. A process entry can be placed on the canvas several times; and each instance of the entry must have a unique name. 


Email Details:


1

To

Provide a comma separated list of email addresses.

2

CC

Provide a comma separated list of email addresses in carbon copy(CC)

3

BCC

Provide a comma separated list of email addresses in blind carbon copy(BCC)

4

Subject

Provide a subject for the email.

5

Email body

Provide contents of email body or a variable.

6

Synchronous

If it is checked the step will wait for response from AE Server. Enable checkbox to make it synchronous with workflow completion.

7

Send Email on last row

Enable checkbox to send one email upon completion of reading the last row.





Attachment Details:


1

Attachment

List of attachments


Set PS Variables 

Description

Set PS Variables entry sets PS Variables with global or local scope as specified. These variables are available in the same process.

Configurations

No.

Field Name

Description

1

Step name

Name of the step.  This name has to be unique in a single workflow.


Field values (Tabular):


2

Variable name

Specify the variable name to be set.

3

Scope 

Specify the scope of the variable (Local or Global).

Note:

Global variables are available throughout the lifecycle of the parent workflow/process. They can be created at any sub-level and it will be available after that to the entire scope. They will be destroyed after the main or parent workflow/process ends.

Local variables are available only in the workflow/process where it has been created. They are not available to the child workflow/process.

The same variable name can be used for global and local scopes simultaneously. The value modified or fetched is completely based on the scope specified as mentioned in the note below. 


Note: 

The PS variables are added to the existing list which pops up on Ctrl-Space where applicable. The format of these variables in the list will be as ${GLOBAL.varname} and ${LOCAL.varname}. The PS variables created in ‘User Defined Java Class’ or ‘Modified Java Script’, are not visible in this list.


However,

If the child workflow/process is already opened and a variable is added in the parent workflow/process. This variable is not reflected directly at design time (i.e. on Ctrl-Space) although there no issues during runtime. There are two options for this,

The user can type the variable name when required
Reopen the child workflow/process (from Open referenced object) after the variable is added

4

Default value

Specify the default value of the variable. 



NoteThe PS variables set in this cannot be used for database connection details.


Common Buttons:

No.

Field Name

Description


Buttons:


1

OK

On click of this button. It will check the field values.  If any required field values are missing then it will display validation error message.

If all the required field values are provided then it will save the field values.

2

Cancel

On click of this button, it will cancel the window and does not save any values.

3

Get Fields

Click this button to fetch the fields from the previous steps in the workflow stream.


Set Workflow Result

Description

The Set Workflow Result is used to set the workflow result on AutomationEdge for the particular request.

Configurations

No.

Field Name

Description

1

Process Entry Name

Specify a unique name for the process entry on the workspace area. A process entry can be placed on the canvas several times; and each instance of the entry must have a unique name. 

2

Success

Boolean value (true or false) can be set to define the request status (Success or Failure). 

3

Status

Status can be set from one of the following: Complete, Failure or Diverted. Status can be set irrespective of value set in Success above.

4

Message

Success or error message to be set for the request. Message is governed by the Success set above.

5

Failure Reason

Failure reason can be set if success is false and status is failure.

Choose from the fourteen failure reasons:

  1. License invalid
  2. Invalid request input
  3. Invalid credentials
  4. Invalid workflow
  5. Agent stopped or restarted
  6. Failed to connect to external system
  7. Workflow failed to internal reason
  8. Error while uploading/downloading file with server
  9. Script exited with errors
  10. Workflow failure set in OUTPUT.txt
  11. Workflow instantiation failure
  12. Exceeded maximum execution time
  13. Too many pending requests
  14. Unknown reason

6

Total Operations

Total number of operations performed

7

Successful

Number of successful operations performed

8

Attribute 1

Additional Attribute 1

9

Attribute 2

Additional Attribute 2

10

Attribute 3

Additional Attribute 3

11

Attribute 4

Additional Attribute 4

12

Attribute 5

Additional Attribute 5

13

Attribute 6

Additional Attribute 6


Output Parameters:


1

Variable

Name of the variable to set

2

Type

Data type of the variable

3

Display Name

Display name of the variable as seen on AutomationEdge UI





      Links to better reach 

            Bot Store

             EPD