Basic JSON structure of the event configuration

the json file created with the solution litmus production record external event configurator, will include the json configuration for one or more events this allows, that more than one event can be monitored for example by the flow from the solution litmus production record event processing flow each individual event consist of a unique event name of three sub sections sub section eventtrigger the first sub section will hold the configuration for the trigger and is setup using the sheet event and trigger definition it consists of the a series of key value pairs 255,278 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type each event has only one trigger condition sub section identifier the second sub section will hold the configuration for the identifiers and is setup using the sheet event identifier definition to learn more about identifiers, please review the chapter how are data recorded in litmus production record database docid\ ulfmhqnmwb91rkntbaqqn the sub section identifier consist of 1 5 sub keys called identifiertagrelation how many of these sub keys exist is based on how many identifiers had been setup for the data model each sub key identifiertagrelation consists of a key value pair and a json sub structure called identifiercollection 255,278 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type each substructure called id consists of a series of key value pairs 255,278 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type each event is required to have at least one and up to 5 identifiertagrelation sub keys each of these sub keys has at least one and up to 5 id substructures note if one sub key identifiercollection has 5 id substructures, no additional identifiercollection sub keys can exist, as only a maximum of 5 identifiers can exist per data model sub section items the third sub section will hold the configuration for the identifiers and is setup using the sheet event item definition to learn more about data models used to store event data in litmus production record database, please review the chapter core concept behind recording production record data via data model docid\ ffsctesqgb9gj7wy5kymo the sub section items consist of 1 n sub keys called itemtagrelation how many of these sub keys exist is based on how many items are to be updated by the event each sub key itemtagrelation consists of a key value pair and a json sub structure called itemcollection 255,278 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type each substructure called item consists of a series of key value pairs 255,278 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type each event is required to have at least one itemtagrelation sub keys each of these sub keys has at least one item substructure