Hi Vinod, Thanks for the suggestion. I will change the format to that way.
Regards, Sameera On Tue, May 3, 2016 at 1:39 PM, Vinod Kavinda <[email protected]> wrote: > Hi Sameera, > Small suggestion. Can we keep these audit logs in a format that is similar > to Activiti audit logs [1]. Since we are using Avtiviti engine in BPS, it > will be better if we have the same format throughout the BPM platform. > > [1] - http://www.activiti.org/userguide/#historyFormAuditPurposes > Regards, > Vinod > > On Tue, May 3, 2016 at 10:52 AM, Sameera Gunarathne <[email protected]> > wrote: > >> Hi all, >> >> I am currently working on $subject. With this functionality[1] Publisher >> will be able to record all the activities performed to the process assets. >> Audit log will record following activities. >> >> - >> >> Adding a process >> - >> >> Editing of process text >> - >> >> CRUD operations on process artifacts such as pdf, bpmn model >> - >> >> Process life cycle change >> - >> >> Configuring of process analytics >> >> >> Implementation >> >> All the actions are done in the publisher is recorded in the Carbon >> Registry log as an entry with the format of (log_id, reg_path, user_id, >> logged_time, reg_action, reg_action_data, tenant_id). From this log >> entries it is needed to filter out the activities mentioned above for the >> each process created in the publisher. The sample log entries for creating >> a process is as follows. >> >> >> >> >> Process creation involves several update operations including adding >> lifecycle history component, initiating process lifecycle(i.e >> SampleLifeCycle2). Therefore this set of operations should be identified >> and logged as the log entry for process creation in the audit log. >> Similarly for CRUD operations done to the process artifacts should be >> logged to the audit log. Therefore the basic tasks to be done are: >> >> >> 1. >> >> Access registry and get process list registered in the publisher. >> 2. >> >> Access registry to get the process wise log entries. >> 3. >> >> Filter log entries to form audit log for each process. >> 4. >> >> View the audit log in PC. >> >> >> Registry is accessed basically for two types of operations. One is to get >> the process list and other one is to get the registry logs for process >> wise. Process wise logs are filtered to separate out log entries for >> process artifacts (pdf, flowchart, bpmn model). Audit log entry formed in >> PC consists with the following parameters: <timestamp, user, process_id, >> artifact_type, action_performed> . >> >> Any thoughts or comments of the described implementation are welcome. >> >> [1] - https://wso2.org/jira/browse/PC-43 >> >> -- >> Sameera Gunarathne >> Software Engineer, WSO2 Inc. http://wso2.com >> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com&h=gAQEswASa> >> Email: [email protected] >> Mobile: +94714155561 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Vinod Kavinda > Software Engineer > *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.* > Mobile : +94 (0) 712 415544 > Blog : http://soatechflicks.blogspot.com/ > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sameera Gunarathne Software Engineer, WSO2 Inc. http://wso2.com <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com&h=gAQEswASa> Email: [email protected] Mobile: +94714155561
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
