Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-4779

SLA due date value in ProcessInstanceLog table is not updated after updating process SLA

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 7.13.3.GA, 7.13.4.GA
    • Business Central
    • False
    • None
    • False
    • Hide
      • Design a BPMN process which has a SLA-Due-Date defined.
      • Start process instance and update the process SLA timer using kie-server REST API
      • After updating SLA timer successfully, check the SLA-Due-Date field from ProcessInstanceLog table, we can see the old SLA due date. Expected behavior is after updating SLA timer using REST API,  SLA-Due-Date field from ProcessInstanceLog table should also be updated.
      Show
      Design a BPMN process which has a SLA-Due-Date defined. Start process instance and update the process SLA timer using kie-server REST API After updating SLA timer successfully, check the SLA-Due-Date field from ProcessInstanceLog table, we can see the old SLA due date. Expected behavior is after updating SLA timer using REST API,  SLA-Due-Date field from ProcessInstanceLog table should also be updated.
    • ---
    • ---

      Customer is updating process SLA using REST API which is supported after fix of RHPAM-4752 jira. After updating process SLA, timer is updated but it didnt reflect in ProcessInstanceLog table. Its reflected only after completing process instance.

       

       

            [RHPAM-4779] SLA due date value in ProcessInstanceLog table is not updated after updating process SLA

            Luz Rodriguez added a comment -

            Hi gmunozfe@redhat.com 

            Do you have any updates on this QA phase?. Verizon is complaining about why this fix was not included in the RHPAM 7.13.5 release.

            Regards,

            Luz Rodriguez added a comment - Hi gmunozfe@redhat.com   Do you have any updates on this QA phase?. Verizon is complaining about why this fix was not included in the RHPAM 7.13.5 release. Regards,

            Neus Miras Chueca added a comment -

            rhn-support-ghu Yes, those PRs fix this issue.  gmunozfe@redhat.com could you take a look there?, only remains your approval

            Neus Miras Chueca added a comment - rhn-support-ghu Yes, those PRs fix this issue.   gmunozfe@redhat.com could you take a look there?, only remains your approval

            Neus Miras Chueca added a comment -

            Hi rhn-support-luzrodri,  the fix is already there but it didn't make it to the recently release cut-off. It only remains the QA review and after that, it  will be on the next release for sure.

            Neus Miras Chueca added a comment - Hi rhn-support-luzrodri ,  the fix is already there but it didn't make it to the recently release cut-off. It only remains the QA review and after that, it  will be on the next release for sure.

            Luz Rodriguez added a comment - - edited

            Hi nmirasch@redhat.com mnovotny@redhat.com

            will this be considered fixed in other future release ? (e.g 7.13.6 ). Verizon is asking for this fix too

            Luz Rodriguez added a comment - - edited Hi nmirasch@redhat.com mnovotny@redhat.com will this be considered fixed in other future release ? (e.g 7.13.6 ). Verizon is asking for this fix too

            Neus Miras Chueca added a comment -

            rhn-support-abhumbe At the end just to consume the rest endpoint to fill the slaDueDate at BC, wasn't enough regarding that column is shown at the process instance list and is also used in queries. The proposed solution was to add a new event to registrer the update and  a listener that adds that new entry to ProcessInstanceLog. Even we have the code almost done,  we  won't have time to merge before the 7.13.5.GA release.  

            Neus Miras Chueca added a comment - rhn-support-abhumbe At the end just to consume the rest endpoint to fill the slaDueDate at BC, wasn't enough regarding that column is shown at the process instance list and is also used in queries. The proposed solution was to add a new event to registrer the update and  a listener that adds that new entry to ProcessInstanceLog. Even we have the code almost done,  we  won't have time to merge before the 7.13.5.GA release.  

            Neus Miras Chueca added a comment -

            hi mnovotny@redhat.com  this is in my todo list. I was planning to work in the next days 

            Neus Miras Chueca added a comment - hi mnovotny@redhat.com   this is in my todo list. I was planning to work in the next days 

            Francisco Javier Tirado Sarti added a comment - - edited

            This does not seems like a bug. The system is working fine (the rest api is returning the right sla value). The sla value will be eventually written to the AUDIT table. The issue is that the sla update by itself, does not trigger an audit update, which I think is perfectly valid.
            Unless this is really causing an issue for the customer, I vote for either nack or at least change to feature request
            rhn-support-alazarot

            Francisco Javier Tirado Sarti added a comment - - edited This does not seems like a bug. The system is working fine (the rest api is returning the right sla value). The sla value will be eventually written to the AUDIT table. The issue is that the sla update by itself, does not trigger an audit update, which I think is perfectly valid. Unless this is really causing an issue for the customer, I vote for either nack or at least change to feature request rhn-support-alazarot

              nmirasch@redhat.com Neus Miras Chueca
              rhn-support-abhumbe Abhijit Humbe (Inactive)
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: