Does no one have any suggestions?
Hi,I don’t think that will solve my actual problem, I think the INPUT_REF_DURATION only moves the “dotted blue line” in PSO, instead of the blue line which is shown like this in the legend:
Thank you for your reply. Is the DSE_ALLOCATION table supposed to be updated continously? We’re currently experiencing that the table has not been updated for 5 days, and seems like there is a large gap between the updated intervals.
Turned out there were a column modified_dttm on request_ext as well as request, and that caused the issue.
Hi,Thanks for your answer. Yes, I am familliar with the documentation. However, my issue is that the fast mode synchronization is not working, and I was wondering if there is any place to enable/disable this functionality, or should it work with the OOTB functionality?
Hi,Yes, that was my initial question, if it was possible to use the same conditions in the dataset to filter in the request screen when navigating from the counter.I guess I’ll have to make it work in another way, thanks for your help.
Hi,Thanks, tried this, a little silly mistake to make. When changing that value, the value is passed correctly to the search screen, however, the filtering created in the dataset is not used in the request search. In this example, we had 13 requests in the counter, but over 1000 requests was found in the search screen.
Hi Sanjeewa,You are correct, that is what I’m trying to do. However, I can’t make it work like I want to. I have a dataset which contains some data, and the conditions in the dataset looks like this (Note that # won’t work for us in the conditions, we need to use $ instead). Note that SALES_GRP_D and user_def17 are conditions that the user can change: And, the element looks like this:However, when clicking on the element, it opens the search in the request screen like this, instead of having actual values:
Hi,Thanks for the reply.I can see that I actually have the “Bulk Activity Change”, but the result is still the same, after commiting all the tasks that are in the bucket, the DSE is overwriting the changes made, and resets the status to Allocated once again. We are using PSO 6.7.0.30, I saw that there were lots of bug fixes to this in 6.8, so I guess that might solve the issueRegarding the “linking” of resources to the buckets, I think you might misunderstood a bit. What I need to understand, which might be easier when solving the issue with commiting the activities, are what is happening to the task in FSM, when the activity is commited to the bucket resource in PSO. In FSM, there needs to be an owner on the task to set task status “Committed”, but the Resource Bucket is not a Person in FSM. Hopefully that made some sense!
Thank you very much, didn’t know I could just enter the columns directly in the content field.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
