Scenario: A manager does not want to be understaffed by granting too many overlapping vacation requests. The manager needs to know how many vacation requests have already been approved before approving any more.
To solve this problem, a workflow process shows all approved vacation requests that fall in the next 50 days. The manager can look at the list and make a good decision on how many requests to grant. All vacation requests are stored in a collection in the process. The Date Range Rule checks the vacation request collection and returns those that occur in the next 50 days. This information is displayed in a webform.
Process: This process is created as a Webforms-type project.
The following screen shot shows the process:
The following screen shot shows the editor for the Date Range Rule component:
The component uses a dynamic model to retrieve the current date.
The following screen shot shows the dynamic model:
The Get Current Date component creates a process variable called CurrentDate that the Date Range Rule editor uses for the value of the base date. Based on this dynamically supplied date, the component calculates 50 days later and chooses its outcome path. In other words, the Date Range Rule uses the current date as the base date. It calculates a date 50 days from the current date to create its range.
Other components in this example are as follows:
This component is a custom component created with the Integration Engine.
For more information on the Integration Engine, see the Workflow Solution Administrator's Guide.