Public Static Collection

Reusable and Static Parameters tool is used to create Parameters that will be used repeatedly through the ensuing configuration of your integration. There is no limit to the number of such Static Parameters that can be added. Each Parameter has a ‘Properties’ Tab within the ‘Parameter Control Panel’. Static Parameters are Parameters that are not received from any system but rather are created within the GLU.Engine.

A Static Parameter can not be Null (Empty).

The Static Parameter is should not be changed throughout the life of the transaction.

Example

Default value

Default value is mandatory.

If added, this acts as a preset value for the Static Parameter to fall back on when it is set to null. Note: It’s not possible to set a default value when the type is set to Timestamp (see below).

Timestamp

Setting the type to timestamp will result in the value of this Static Parameter being set to a datetime structure. The date is assigned when requests are received.

There is no format for timestamp it is simply saved as a ‘LONG’ format.

If you want to Format the timestamp there are two ways:

1. In the Parameter Control Panel within the Un/marshalling tab you can set the Date Format – the default is dd/MM/yyyy.

2. Derived Parameters have a function called DATEFORMAT(${yourtimestamp}.

The timestamp is set to the time when the transaction is first initiated and it is kept static throughout the flow through the application. This means if the flow moves to other transactions in the application, even though the flow is in another transaction the timestamp value will still be the same.

The diagram illustrates how it is possible to navigate between transactions, however the timestamp will always stay the same.

In orchestration, if a connector is called, the flow moves out of the application. When the flow returns then the timestamp value will still be the same. This is the case for synchronous and asynchronous connections.

Timestamps versus NOW variable

Timestamp values are always static through out the transaction in the application. This is not the case for variables defined as ${NOW}.

NOW valuables only reflect the time at the point the value is used.

Was this article helpful?

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Need Support?

Can't find the answer you're looking for?
Contact Support
Fill the form and we’ll contact you shortly

    I agree with

    cookies
    We uses cookies to make your experience on this website better. Learn more
    Accept cookies