Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Date Greater Than

Created: 13 Jun 2012 • Updated: 10 Jul 2013
Language Translations
Collaborators: SymantecWorkflowTeam, Chan Eil Fhios
SymantecWorkflowTeam's picture
0 0 Votes
Login to vote

Date Greater Than

Component definition

This component compares a date with another date to determine which is "greater" (occurring later). The component follows the appropriate outcome path based on the result of the date comparison. Both dates can be constant or process data.

Component icon


Description of component output paths

Unknown

The component output paths are described in the following table:


Property

Description

true

The path that is followed if the first date occurs after the second date.

false

The path that is followed if the first date occurs before or at the same time as the second date.

Description of component tabs and their properties

The properties on the Configuration tab in the Date Greater Than component are listed and described in the following table:


Property

Description

First Date Variable Name

The variable name for the first date you compare.

A variable array value can be selected when you drill into the array and select a value.

Second Date

The date or the variable name that contains the date you want to compare your first date against.

A variable array value can be selected when you drill into the array and select a value.

Second Date is Minimum

If Second Date is Minimum is checked, Second Date becomes the minimum value (usually 01.01.0001). This minimum value is useful for assuring that the first date is not zero.

The properties on the Settings tab in the Date Greater Than component are listed and described in the following table:


Property

Description

Component Class Name

The class name of this component. This property is not editable, but useful if you call Symantec support.

Description

The description of this component. This property lets you describe how the component is used. You can use it to provide any wanted
documentation for this component.

This description is included in
the model reports that are created when you click Plugins > Generate Business Model.

Location

The physical location of the top left point of this component on the
workflow model.

Name

The name of this component. You can change the name.

If you changed the component name when you double-clicked it on the workflow model, the changed name appears here.

Override Background Color

This property lets you change the background color of this component.

To Do

This property lets you record what you still need to do with the
component. Use this property to help you remember the configuration that you want to apply to this component.

The text that you enter for this property appears at the bottom of the component editor. If you enter text for this property, a checklist symbol appears on the component in the workflow model.

Is Enabled

This property lets you enable or disable the component. By default,
components are enabled. When a component is disabled, it has no
effect on the Project. Uncheck Is Enabled to disable the component.

  • Execution Outcome

    If a component with more than one outcome
    path is disabled, you must select which outcome path you want the component to take. Click the Execution Outcome drop-down list and select the outcome path for the workflow to follow.

  • Disabled Mapping

    If the component has output parameters, you must configure all output parameters with fixed data to pass on. This configuration can be performed in the Disabled Mapping option.

Connection information

Not applicable

Component settings

Unknown

Use cases

Some examples for the Date Greater Than component are as follows:

  • Hardware order request

    A hardware order request includes a requested delivery date field. The Date Greater Than component compares this variable to the current date to ensure that the requested date is not before the current date.

Hardware order request

Scenario: A hardware order request form includes a requested delivery date field. This information helps the purchasing department order and deliver hardware requests according to priority.

Process: This process is created as a Forms (Web) Project type.

The following screen shot shows the process:

The following screen shot shows the run-time form:

The Delivery date requested box creates a variable called RequestedDate. The date that is requested must be after the current date. A Date Greater Than component compares RequestedDate against the current date.

If the RequestedDate variable is not later than the current date, the Date Greater Than component renders a "false" outcome path. The false outcome path sends the requester back to the form, where an error message prompts for correction.

The Get Current Date component is essential in this process. It creates a current date variable that the Date Greater Than component uses in the comparison.

This method of date validation can be applied to a variety of date-specific situations, which includes vacation requests, deadline/gate control, and scheduled maintenance notifications.

Other components in this example are as follows:

  • Form Builder

  • Get Current Date

  • Send Email