BPM, Workflow, and Case

 View Only
  • 1.  the token does not proceed to next activity

    Posted Mon August 08, 2022 04:04 AM

    Hello Team,


    I faced an issue in the BAW environment when completing any task with a user, the token does not proceed to the next activity. 


    When debugging instance, completing a task from coach, and showing Locations on debug screen found that the token was in the same activity and did not move from the current activity with the message "the task was closed by username".


    - this problem occurred at all process applications in this environment. and if I take the process app to another environment no problem occurred.


    need your support


    Best Regards,
    Mahmoud Abdelmonem
    J2EE, IBM BAW developer

     



    DataServe
    www.dataserve.com.sa
    The information contained in this message is confidential and may be legally privileged. It is intended only for the person named above. If you are not the named addressee, you should not disseminate, distribute, copy, disclose or use this message or its contents. If you have received this message in error, please notify the sender immediately and delete this email from your system. Thank you.
    National DataServe & Turnkey Solutions Co.
    Registered office: Rossais Comm. Center, Olaya Street, 10th floor, Kingdom of Saudi Arabia P.O. Box 69106, Riyadh 11547


  • 2.  RE: the token does not proceed to next activity

    IBM Champion
    Posted Mon August 08, 2022 10:02 AM
    Hi Mahmoud,

    Have you tried restarting the server ? Do you see any error in the logs ?
    Is the event manager up and running ?


    ------------------------------
    Atanu Roy
    Solution Architect
    Salient Process
    ------------------------------



  • 3.  RE: the token does not proceed to next activity

    Posted Tue August 09, 2022 03:01 AM
    Hello Atanu,

    Firstly, Thanks for your support.

    After searching, we found user credential at WebSphere is expired or deactivated from LDAB. this user used to connect external Filenet Server.
    we change username with another active one> restart server then it is solved


    ------------------------------
    Mahmoud Abozaid
    ------------------------------