Stored Processing Information

Owned by Dmitry Donosiyan (Unlicensed)
Last updated: Nov 08, 2024 by Kinga Huszno
2 min read

Data stored is:

  1. File correlation id – to correlate incoming file and all information about this file, same as signal correlation id.

  2. Remote file name – original filename of the file.

  3. Added timestamp – timestamp of file acceptance on region. Combined with remote file name it allows the user to understand what is this file, if it should or not be processed.

  4. Status – to store information about status of file processing, if the file was acknowledged as file for some of workflows and pending for processing, if the file was already processed, if the file was not acknowledged as data for any workflow on region and if file processing was canceled before actual file load. Needed for user to be able to understand what happened with the file.

  5. Source signal correlation id – only for files that were created from incoming file as result of profile_executor processing.

  6. Process wrf + wrf + event names and process wrf + wrf + event corrIds for already processed files – information about procWrf/wrf/event that will process/already processed file. Needed for user to understand what will happen/what happened with file.

  7. Sent by – must store information about user who sent this file (if file was sent through MCC/MCE) or owner of the file (for instance sitesee adds itself as owner of the file to file properties) or profile under which this file was sent to processing

  8. Source file name – name of source file from which this file was generated – only for files that are created from external data as part of profile_executor processing.

  9. Consumed/cancellation timestamps – timestamps when file was processed or file record was deleted from queue for processing

  10. Cancellation correlation id – correlation id for the RTR removing the file from the processing queue.

  11. Canceled as child flag – if file was canceled as child of incoming file. For instance, if user sends incorrect SRM file that is processed in profile_executor workflow and creates GenericSMF and Rating files for profiled generic load user must be able to cancel all files that were created from source SRM file.

  12. isBundleTrigger flag – if the file is a bundle trigger and instantiated workflow

  13. triggeredWrofklowCorrId – correltation id of workflow that is triggered by this file if the file is a bundle trigger

  14. genericloadprofile – name of profile if the file belongs to a specific generic load profile

  15. ErrorDescr – detailed reason of failed/NACK status

  16. Queue instance – specifies the queue to which the file belongs.

Here is a table of information supposed to be stored, corresponding DB fields for data storage, logic of data origin and possible values.