Abstract: According to some embodiments, systems and methods are provided including receiving a definition for a scenario including a plurality of operation steps, wherein a first and second operation step is executable by a respective first and second application under test; recording a first and second test script for the respective first and second operation steps of the scenario with a respective first and second test automation tool; receiving a first and second test script identifier for the recorded respective first and second test script at a persistence proxy layer; updating the definition of the scenario; receiving the recorded first and second test scripts at an orchestrator; identifying one of the first application under test and the second application under test for each operation step in the updated scenario; and executing one of the first and second test scripts based on the scenario definition. Numerous other aspects are provided.

Abstract: A method includes determining a correlation feature shared among at least a portion of a plurality of tracking documents including a first tracking document and a second tracking document. The method includes receiving a first batch of tracking documents associated with a logistics process. The tracking documents includes the correlation feature and logistics information associated with the logistics process. The method includes generating a first correlation between the first tracking document and the second tracking document. The method includes receiving a second batch of tracking documents. The second batch includes a third tracking document including a change in the logistics information indicated by the first tracking document. The method includes generating a second correlation between the third tracking document and the second tracking document. The method includes sending a status of the logistics process. Related systems and computer program products are also provided.

Abstract: Systems and processes for recording operational activities in a traceable manner are provided herein. Event data for events associated with operational activities may be received at a system, the event data including, for each of the events, a time parameter and a subject of the respective event. The events may be grouped and processed according to the time parameter or the subject of each of the events, and one or more database tables of a model may be populated and/or updated with event entries based on the event data. The model may include a first part corresponding to processing of the operational activities, and a second part corresponding to results of the processing of the operational activities, where event entries stored in the first and second parts of the model are linked by respective process dates for the event entries. The tables may be output for presentation to a user.

Abstract: Technologies described herein can be used for the bulk lazy loading of structured data from a database. A request can be received to initialize an application data structure (such as a structured data object, a hierarchical data structure, an object graph, etc.). The data structure can be analyzed to identify a plurality of child objects of the data structure. Database records associated with the plurality of child objects can then be identified. A loaded child record table can be inspected to determine which of the identified database records are not stored in a cache. A request can be generated, comprising one or more queries to retrieve the uncached subset of database records from the database. Once the uncached subset of records are received from the database, these records can be used, along with the cached subset of the identified database records, to initialize the plurality of child objects of the application data structure.

Abstract: Systems and processes for recording operational activities in a traceable manner are provided herein. Event data for events associated with operational activities may be received at a system, the event data including, for each of the events, a time parameter and a subject of the respective event. The events may be grouped and processed according to the time parameter or the subject of each of the events, and one or more database tables of a model may be populated and/or updated with event entries based on the event data. The model may include a first part corresponding to processing of the operational activities, and a second part corresponding to results of the processing of the operational activities, where event entries stored in the first and second parts of the model are linked by respective process dates for the event entries. The tables may be output for presentation to a user.

Abstract: Technologies described herein can be used for the bulk lazy loading of structured data from a database. A request can be received to initialize an application data structure (such as a structured data object, a hierarchical data structure, an object graph, etc.). The data structure can be analyzed to identify a plurality of child objects of the data structure. Database records associated with the plurality of child objects can then be identified. A loaded child record table can be inspected to determine which of the identified database records are not stored in a cache. A request can be generated, comprising one or more queries to retrieve the uncached subset of database records from the database. Once the uncached subset of records are received from the database, these records can be used, along with the cached subset of the identified database records, to initialize the plurality of child objects of the application data structure.