Technical Monitor in
T24
AA Technical 5:
Activity API
Swetha S
Objectives and learning outcomes
• After completing this presentation, we will be able to:
• State the need for [Link] property class
• Create property and product condition for [Link]
• Understand how [Link] works
Scenario
• When an Activity LENDING-DECREASE-COMMITMENT is performed on a
revolving loan, the user should be able to input the value of [Link]
that will automatically affect the Arrangement’s Account.
• What would be the solution?
• No routines can be attached to the versions [Link]
• Hence, we would need to go with the [Link] property class defined
specifically for this purpose.
[Link] Property Class
• Steps involved to attach the routine to an Activity/Activity Class
• Write a routine, compile/catalog it
• Create an [Link] entry
• Attach it in Activity API product condition
• Any number of routine can be attached to the same Activity/Activity Class.
• The routines can be attached either as a pre-routine or a post-routine. A pre-
routine is one that will get executed before an activity takes place and a post-
routine would get executed after an activity.
[Link] Property Class
• [Link] is a cumulative property. Cumulative, as the name implies is, when
a child and its parent product have routines defined, routines defined at both
levels will get executed.
• During proofing a product with [Link] property following is the order in
which the records are merged:
• Routines attached at Child followed by Parent
• Routine attached for an Activity
• Routine attached for an Activity Class (If no routines are attached at the
Activity level)
• Hierarchy of routine execution:
• Pre validation routine triggered prior to core validation.
• Pre routines followed by Post Routines.
Back to Scenario
• When an Activity LENDING-DECREASE-COMMITMENT is performed on a
revolving loan, the user should be able to input the value of [Link]
that will automatically affect the Arrangement’s Account.
• What would be the process involved?
• Create a local reference field for Posting Restriction in the [Link]
property class and attach it to the version for LENDING-DECREASE-
COMMITMENT using Activity Presentation for the user to enter.
• Create a routine that will pick value from this and update the arrangement
account’s [Link] ([Link] entry for the routine)
• Create a product condition called API, attach the product condition to the
activity class LENDING-DECREASE-COMMITMENT.
• Attach the condition to product, and proof & publish the product.
Step 1 – Local Reference
• Creating the Local Field and attaching it to [Link] property class
Step 2 – Version changes
• The field can be added to the version attached to LENDING-DECREASE-COMMITMENT (or a
version can be newly created and attached)
Step 3 – Routine Creation
• Create a routine that picks value from this field and triggers LENDING-UPDATE-ACCOUNT in
order to update the Actual posting restriction for the loan.
*-----------------------------------------------------------------------------
SUBROUTINE [Link]
*-----------------------------------------------------------------------------
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_AA.[Link]
$INSERT I_F.[Link]
$INSERT I_F.[Link]
*-----------------------------------------------------------------------------
GOSUB INITIALISE
GOSUB [Link]
RETURN
Step 3 – Routine Creation
INITIALISE:
* get standard selection record
[Link] = "[Link]"
[Link] = ""
CALL [Link]([Link], [Link])
* Get the field name of the posting restrict field
[Link] = [Link]
[Link] = ""
CALL [Link]([Link], [Link], [Link],
"", "")
RETURN
*-----------------------------------------------------------------------------
[Link]:
GOSUB [Link] ;* get the details of the arrangement from local variables
GOSUB [Link] ;* map the posting restrict fields
GOSUB [Link] ;* Generate new activity to update post restrict
RETURN
Step 3 – Routine Creation
*-----------------------------------------------------------------------------
[Link]:
[Link] = c_aalocArrId ;* New arrangement
[Link] = c_aalocArrangementRec ;* Arrangement record
[Link] = c_aalocArrActivityId ;* Arrangement activity id
[Link] = c_aalocActivityId ;* Current activity id
[Link] = c_aalocActivityEffDate ;* Date on which activity was triggered
* Get the property for the ACCOUNT
[Link] = "ACCOUNT"
[Link] = c_aalocProductRecord
PROPERTY = ""
CALL [Link]([Link], [Link], PROPERTY)
RETURN
*-----------------------------------------------------------------------------
Step 3 – Routine Creation
[Link]:
[Link] = PROPERTY
[Link] = [Link]:":1:1"
[Link] = ""
[Link] = "[Link]"
[Link] = "[Link]"
[Link] = ""
CALL [Link]([Link],[Link],[Link])
[Link] = [Link]([Link])<1,[Link]>
[Link] = [Link]
[Link] = ""
CALL [Link]([Link], [Link],
[Link], [Link])
RETURN
Step 3 – Routine Creation
[Link]:
* form the secondary activity id
[Link] = [Link]<1>
[Link] = "UPDATE"
[Link] = PROPERTY
[Link] = [Link]:"-":[Link]:"-":[Link]
CALL [Link]([Link], [Link], [Link],
"", [Link], [Link], [Link])
RETURN
*-----------------------------------------------------------------------------
END
Step 4 – Creating API Condition and attaching routine
Step 5 – Attaching Condition to Product
Decreasing Commitment for an existing loan
Once Activity is triggered
Once Activity is triggered
Summary
• In this presentation, we discussed the following:
• Need of [Link]
• Creating a Local Reference for user input of Posting Restriction during
LENDING-DECREASE-COMMITMENT which was then applied to the
arrangement’s ACCOUNT property through [Link]
Technical Monitor in
T24
THANK YOU
