Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    12
  • Answers answer
    1
  • Subscribers subscribers
    171
  • Views views
    953
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

After I switched target states in a transition and deployed, why do items in the UI still transition to the old target state?

pbustin

In Composer, I added a state to a workflow, and switched the target state of a transition to the new state; however, after deployment from Composer to the test environment, items in the UI are still transitioned to the former target state.  I had originally duplicated the state from an existing state, but on account of the UI behavior I just described, I deleted the new state and created a replacement from scratch; that didn't change the behavior.

There is no Action defined in the new state.  In the transition, I added an action to create a sub-task, and deployment was successful for that.

I duplicated an existing transition to connect the new target state to the former target state.  I would as soon not replace the duplicated transition from scratch, because it contains many field overrides, but I can if I must.

I no longer have Micro Focus Support for SBM; only for PVCS, but I'm hoping the Community can still be a resource for me for this unusual event.

  • 0  

    Hi Phil, 

    What you are saying doesn't sound possible.  Perhaps, the Composer UI only appears to have switched the target state of the transition.  View the transition in TS_TRANSITIONS and verify the new state id; it is likely still set to the original state.  If you confirm this, edit the transition in Composer using the properties dialog.  Perhaps, switch it to a different state and back again.

    David

  • 0 in reply to   

    Hi David and Phil,

    I have come across this oddity when deploying new workflows, try clearing your browser cache. Not sure if this helped or just giving it a bit of time to "figure out" the new workflow. Hope this helps. 

  • 0 in reply to 

    I tried clearing browsing data, but no change.  I recall that there's another procedure, more complicated, to do this in Chrome, specific to SBM, I think, but I don't remember it.  Also, if cache is the problem, why did a new action on the transition get deployed, but not the destination state?

  • 0 in reply to   

    Toad shows the correct destination state.

  • 0 in reply to 

    For chrome I open the settings page and then search from cache or paste (chrome://settings/clearBrowserData?search=cache) into the chrome URL bar. 

    Make sure to select Advanced, click all time, and make sure every box is checked. 

  • 0 in reply to 

    That is what I tried.

  • 0   in reply to 

    And an Incognito tab does not help?

  • 0 in reply to   

    Sorry, I don't know what that means.

  • Suggested Answer

    0   in reply to 

    Hey Phil... The top of the browser says "incognito" after you open a private browser tab:


    If the problem is not browser cache, maybe the Tomcat is stuck. You could try stopping Tomcat, deleting the files/folders in side the Tomcat\work and Tomcat\temp folders, stating Tomcat. It will take longer than normal to start because it's rebuilding all the cache, but it might be worth a try.

  • 0 in reply to   

    I did a couple of GETs of referenced workflows (Global and 1 other) that were probably unnecessary, and exported the most recent deployment to Production; imported all to Composer, and added my new state and transition from scratch.  That didn't work either; nor did Incognito.  Would restarting the server after hours be as effective as restarting Tomcat?  Would I also have to delete the files and folders you mentioned?

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.