The Batch Stamp activity signifies that all needed corrections to the project have been made, and the plans can now be stamped. This activity is usually found at the end of a workflow. When a user kicks off a batch stamp, it creates a scheduled task. The user now becomes the owner of the task. The scheduled task notifies the user when the task is completed or failed.

Automated Batch Stamp Properties

Batch File Stamp Template Name: Specify the batch file stamp template name to use for automated batch stamping.

Folder Name: Specify a pipe delimited list of valid Folder Names for the Project where the batch stamp will be applied.

Notify Group Name: Specify a valid Group Name for the Project that will receive an email notification when the automated batch stamp is completed or when error occurs.

Scheduled Task ID: The task ID for the BatchStampTask. This is used for debugging purposes for technical support.

General Properties

Disable Activity (checkbox):  Allows the disabling of the activity. If checked, the activity will be greyed out in the designer and will be skipped in the workflow process.

Stop After Processing: Determine if this activity should stop after execution or continue processing the children activities. This is helpful in debugging and walking through the workflow one activity at a time.

Custom Code: Used to access the custom code for creation or editing. This 100% web-based feature allows creation of custom code, typically used for integrations. The code can run at different times in the workflow, such as before, during, or after the activity has been initialized.

Activity Timer Interval: The interval of time that must pass before the activity is executed inside the workflow engine a subsequent time. The interval will only be in affect when there are no accepted or pending tasks on the activity. Timers are generally used in combination with custom code so that the activity is only executed every X minutes instead of every time the workflow engine fires (i.e. check if fees are paid every 4 hours). The minimum allowed time lapse is 5 minutes.

Icon: Specifies the image name for activity icon shown on the eForm.

Startup Tasks Properties

In this section of the activity properties, startup tasks can be created or modified within the Workflow Task Manager. A maximum of 3 startup tasks can be created.  

The following fields are found within the Workflow Task Manager screen:

Assignment Type: This dropdown allows a choice between making the startup task an Individual, First in Group, All in Group or Assign to Workflow Owner task. For definitions of each of these kinds of assignments, click here.

Group Name: Used to specify the group that will receive the task when it is created.

User Name: Used to assign task to a specific user through email.

Priority: Used to determine the priority of the startup task.

Task Name: Used to specify a name for the startup task.

Task Instructions: Used to specify the task instruction to display on the eForm.

Custom URL: Used to direct the user to the specified URL. When the task is opened, it will redirect to the URL in this field.

Due Days Out: Allows for the designation of a due date for the startup task.

Task Properties

Exclude Task from Review Cycle: This property will tell the system to exclude the review cycle number from the task so any tasks created for this activity will not be linked to a specific review cycle.

Disable Task Assignment Emails: Determines if email notifications will be disabled for this activity.

Task Assigned Notification Template: Used to specify which email template shall be used when the activity is spawned.

Task Completion Email Notification Template: Specifies the email template used to notify the user when the task is complete.

Task Notification Reminders

The fields in this section enable the programming of reminder emails, including which template should be used and what the interval of the emails should be.

Time to Start Notifying Before Task Due: How many days and/or hours before the due date that notifications will start being sent. For example, if this is set to 5 days then notification emails will start being sent 5 days before the due date. How many notifications that are sent depends on the Notification Interval setting.

Task Before Due Notification Interval: The amount of time in days and/or hours between each notification that is sent. For example, if the task due date is 5/30, the interval is set to 2 days and the time to start notifying is set to 10 days then notifications will be sent on the following days:

5/20 - notification #1

5/22 - notification #2

5/24 - notification #3

5/26 - notification #4

5/28 - notification #5

Task Before Due Email Notification Template: The email template used to notify users before the task is due.

Task Past Due Notification Interval: The amount of time in days and/or hours between each past due notification that is sent. For example, if this is set to 2 then notification emails be sent every 2 days after the due date has passed.

Task Past Due Notification Limit: The total number of notifications that should be sent after the due date has passed. For example, if the task was due on 5/1, the interval is set to 2 days and the notification limit is set to 3 then notifications will be sent on the following days:

5/3 – notification #1

5/5 – notification #2

5/7 – notification #3

Task Past Due Email Notification Template: The email template used to notify users after the task is due.