Hi all, what approach should be taken while configuring tempo records/ reports..

Hi all, what approach should be taken while configuring tempo records/ reports...Common Objects (because Common Objects use type!)or a!?Are Common Objects going to be updated using a! or are they going to be deprecated?

TIA,...

OriginalPostID-83796

OriginalPostID-83796

  Discussion posts and replies are publicly visible

Parents

  • Hi Sikhivahan, the Common Objects Application will contain rules that can be used in configuring tempo reports and records. Currently, the rules are prefaced with rule!APN_*.
    In configuring SAIL expressions in 7.2, the components are prefaced with the type! domain.
    With Appian 7.3, SAIL Functions use the a! domain instead of the fn! domain used in most other Appian functions. You are required to indicate this a! domain when calling your SAIL functions. The use of a! instead of type! also provides a cleaner appearance of the code.
Reply

  • Hi Sikhivahan, the Common Objects Application will contain rules that can be used in configuring tempo reports and records. Currently, the rules are prefaced with rule!APN_*.
    In configuring SAIL expressions in 7.2, the components are prefaced with the type! domain.
    With Appian 7.3, SAIL Functions use the a! domain instead of the fn! domain used in most other Appian functions. You are required to indicate this a! domain when calling your SAIL functions. The use of a! instead of type! also provides a cleaner appearance of the code.
Children
No Data