Configure date service attributes

In the Management Portal at Service Catalog, on the Attributes tab of the service page, configure date attributes to store a date. This is useful in workflow actions in which users need to provide a date in a fixed format, e.g. an expiration date or a birth date. In the Web Portal, users can provide this date with a date picker.

Configuration

Item

Explanation and Tips

Restricted information

Mask the attribute value in the Management Portal. This ensures you can be compliant with the privacy laws of your country or organization, as unauthorized administrators do not have access to private information like e-mail addresses, phone numbers, social security numbers, etc. This functionality applies to the Management Portal only; restricted information is still shown in the Web Portal.

  • Authorized administrators see the icon Eye-outline-vector-256-256 for restricted attributes and their placeholders anywhere in the Management Portal. They can click this icon to view their value. These values are hidden again when the page is refreshed. This prevents situations in which unauthorized administrators can view restricted information by shoulder surfing authorized administrators. Where appropriate, a button is available to view ALL restricted attributes at once.
  • Unauthorized administrators see the icon Evil eye for restricted attributes and their placeholders. At Transactions, restricted attributes are shown as [attributename]. Although unauthorized administrators can't see the attribute value, this still allows them to verify if the context or definition of the attribute is correct.
  • You can set administrative permissions on this functionality.
  • The value is also restricted if it is determined by a restricted service attribute, people attribute or people identifier.

Date

Select an initial value with a date picker.

  • Clear the field if the date needs to be provided during the service transaction, and it should not be possible to select a previously configured date.

Date at the start of transaction

Resolve the initial value dynamically to the start date of the service transaction. This is useful in services that onboard a new user: when a user is added to the system, you can register dynamically when this happened.

Person attribute

Base the initial value on a text people attribute.

  • The value of the attribute must resolve in an accepted format:
    • YYYY-MM-DD
    • YYYY/MM/DD

Service attribute

Base the initial value on a service attribute of another service (either text, date or datetime).

  • The subscriber to the current service must already subscribe to the other service before the value of its service attribute can be resolved.
  • The value of the attribute must resolve in an accepted format:
    • YYYY-MM-DD
    • YYYY/MM/DD

You can force mandatory input by enabling Attribute may not be empty after workflow input from actor.

Placeholders

When you insert date service attribute as a placeholder in actions, you can retrieve its value:

Placeholder

Explanation

#Service[{attributename}]

Resolve the value of the date service attribute, e.g, 20170102 (YYYYMMDD).

#Service[{attributename.LocalFormat}]

Translate the value of the date service attribute to the user's local date format, e.g. 02/01/2017 for EU, 01/02/2017 for US. Local date format is based on the user's browser settings.

  • Use this placeholder only in services that users can request in the Web Portal; this placeholder does not resolve in auto-provisioned services.

#Service[{attributename}.Description]

Resolve the description of the attribute, e.g. "This is the selected date of the actor".


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other