Getting Started
- ActiveAdd Atarc Process Record to Atarc Process Setting
- ActiveUnit Test for Apex Helper
- ActiveNext Steps
Add Atarc Process Record to Atarc Process Settings
The last piece in order to make this work is to tell the ATARC engine that the apex class "AccountNameChanger" needs to run for the sobject were we setup the ATARC engine previously, additional for what particular trigger event will execute.
For this example we will tell the engine that "AccountNameChanger" will be hooked to the Account sobject, for the BeforeInsert trigger event.
So we add an record entry in the custom metadata type ATARC Process Settings. This is how the entry should look:
Label
|
ATARC Process Setting Name
|
ApexHelperClassName
|
SObject
|
Event
|
IsActive
|
IsAsync
|
Order
|
DependsOnSuccess
|
DependsOnFailure
|
Debug
|
DebugLevel
|
breakIfError
|
Isolate
|
General Availability
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ChangeAccountName
|
ChangeAccountName
|
AccountNameChanger
|
Account
|
BeforeInsert
|
true
|
false
|
1
|
true
|
DEBUG
|
false
|
false
|
true
|
Make sure IsActive and General Availability are checked.
So, the ATARC Process Setting Name (api name is DeveloperName) field is an identifier, you can use this field to give a name to the Atarc Process to be use by the atarc api but be aware it should respect the custom metadata type name rules (i guess it should be unique and not having double underscores together and so on...)
So when creating a new Account record with Hey name, the engine will execute the Atarc Process previously created and the name of the account should change to Yo.
Next - Unit Test for Apex Helper