Posted: 1 Nov 2017 11:23 EDT Last activity: 3 Nov 2017 14:40 EDT
Unable to update or close covered work object in open tab/thread
This is really a question more than a bug.
I have both the Cover and covered work object open and locked in separate threads.
Changes on the parent (Cover) require me to make changes to the child (Covered).
I can identify the thread the child is in and close the thread allowing me to then open the child, update it and save the changes. However, this leaves the tab unchanged in the UI. Therefore if the user clicks the link to the child from the parent in the "Open Tasks" area original and now the stale tab is used.
I have been able to clear the child from the "recent" list but can not solve the navigation from the "Open Tasks".
While working on the parent and submitting an assignment I need to ability to update the child.
As I said this can be done in one of two ways. I either need to get a handle on the thread the child is in and somehow update it there.
Or I believe the easiest thing to do is close the child thread and then procedurally update the child in the parent thread by doing and obj-open/update/save.
The issue I have is that I can largely do the second option but I am still left with essentially the child tab on the client.
So, in short, I’m asking is there a way using pyCaseManager7 portal to close an open tab( I use the word tab loosely as it’s not a visible tab) from within a different thread in another tab.
So, I have a cover and covered work object open and can navigate to either via recent. From the cover on click of a Button, I want the tab/container/thread to be closed for the covered.
You have a bit of a sticky situation. If you know that the user hasn't done any work on the child, you can set the tab to refresh when clicked into and have the refresh do an Obj-Refresh-And-Lock, or similar to get the latest data from the database/deffered list. However, if the user has started filling in fields, this will blow that work away, which will be annoying to say the least. However, not doing this means that when the form gets submitted, you will overwrite the work you just did with stale data from the client.
You will have that problem, no matter what you do about manipulating the content of the thread on the server. I don't really know a great way to address this, but I also don't do a ton of UI manipulation, so there may be things that other folks can suggest to dynamically update fields (do you know what you are changing? Is it a relatively small number of fields? Are they ones that the user would be updating? Perhaps you could just refresh the section(s) that contain them?).