4194
Points
Questions
11
Answers
381
-
- 1733 views
- 1 answers
- 0 votes
-
Here’s my idea; I think tomcat is not starting properly so kill all Java process & start the tomcat again. You might be experiencing some port conflict. There must be a log somewhere since without that info it is really hard to detect the source of your issue. You may also want to start the server in nohup mode to see the nohup log at a minimum.
- 4545 views
- 5 answers
- 0 votes
-
Can you identify the files that are missing (or how are you aware that they are missing)? Can you trace to the time stamp that the ATO should have been created and checked the log files for exceptional events? Is there any pattern that you can ascertain? Have you looked over your subscribers to check if anything has changed? If the logs are not showing any issue then it may lie elsewhere. I would look to see if you can find a pattern, time of day, type of ATO expected, etc… Have you looked in the destination folder? What processes are picking these files up? Does it clear the folder after it processes the file? If so another thought is to check the downstream process for errors.
Which really doesn’t answer your original question yet trying to throw out troubleshooting ideas for you.
- 2234 views
- 2 answers
- 0 votes
-
- 2211 views
- 6 answers
- 0 votes
-
- 2211 views
- 6 answers
- 0 votes
-
Oh I see. You may want to notify the user that sometimes these global searches are many! My company has over a hundred folders and counting! So I would not recommend it. But alas, there is no out-of-the-box way to set these folder to expand. You may just direct the user to to click the ‘expand all’ button at the top of the window.
- 2211 views
- 6 answers
- 0 votes
-
Divakar,
Unfortunately there is no conditional field requirements in Agile PLM such that you may find in other enterprise applications such as SFDC where you can easily handle this type of requirement.
The best you can do here is to manage this through the workflow criteria in the following manner;
IF ‘Field1’ is ‘Yes’ AND ‘Field2’ is NOTNULL then you may enter the workflow
additionally
IF ‘Field1’ is ‘No’ then you may enter the workflowThese two criteria would stop anyone from entering the workflow if your requirement is not meant. Since there is no information that Agile will tell you if the workflow is not enabled (such that ‘Field1’ is set to ‘Yes’ yet ‘Field2’ remains NULL) you can add a validation PX that would better express the missing information. Something akin to an ‘Actions’ menu PX that would better explain the error to the user.
One other thing on my mind is that is ‘Field2’ is indeed NEVER mandatory unless ‘Field1’ is set to ‘Yes’ then you could hide ‘Field2’ using read level rights until ‘Field1’ is set to ‘Yes’… this may cause the user to take note of the additional requirement when faced with the new field suddenly popping up on the object. Just a thought of course.
- 2300 views
- 3 answers
- 0 votes
-
- 3114 views
- 2 answers
- 0 votes
-
- 2163 views
- 1 answers
- 0 votes
-
- 2947 views
- 4 answers
- 0 votes