a!startProcessLink() is showing different behavior at different place

Certified Associate Developer

I have an issue related to a!startProcessLink() function. According to my current scenario on task tab inside tempo, When user opens any task there is a link which on click opens a new interface form. After clicking OK button inside the interface form which is opened by the link, User is again navigated to the task page where exactly the link is available. This is the expected behavior but what happen is the same task form is getting opened from sites page and when user click on the link and subsequently click on OK button inside the interface form which is opened from the link, In-spite of getting to the task page they are redirected to the parent page from where they had launched the task.  

for eg: Inside Tempo

Tasks>Task1(here the link is available and after clicking>Interface form(it contains OK button),

So If user clicks on the OK button the control is again transferred to Task1 page. Now, On Site

 

Site>Task Queue> Task1(link)>Interface form(OK Button), 

If user clicks on OK button here then in-spite of getting redirected to Task1 they will redirected to Task Queue. I used a!startProcessLink() function to accomplish this facility. Can somebody tell me why exactly it is happening?

  Discussion posts and replies are publicly visible

Parents
  • I am also facing same issue, can someone pls provide any suggestion here ???

    Tempo and site behavior are different.  we use site more.  Tempo behavior is as expected behavior, but from Appian site we need to search that task again from main site home page.

  • 0
    Certified Lead Developer
    in reply to JiggnaThaker
    As I understand, it looks like when you start a new Process using the a!startProcessLink, it instantiates a new process instance successfully (as you see the expected interface form). On click of OK you expect the next task/interface to be loaded but the control is broken. This very well could be a problem with activity chaining. But in case you have already looked at that then I would suggest you try to play around with with or load.
    Sometimes using a load() instead of with() or vice versa might solve the issue.
    Please note a load() inside a with() breaks the with()
Reply
  • 0
    Certified Lead Developer
    in reply to JiggnaThaker
    As I understand, it looks like when you start a new Process using the a!startProcessLink, it instantiates a new process instance successfully (as you see the expected interface form). On click of OK you expect the next task/interface to be loaded but the control is broken. This very well could be a problem with activity chaining. But in case you have already looked at that then I would suggest you try to play around with with or load.
    Sometimes using a load() instead of with() or vice versa might solve the issue.
    Please note a load() inside a with() breaks the with()
Children