Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
3 replies
Subscribers
5 subscribers
Views
1096 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
Not able to pull the deadline for a task or process below is the code used.
sarikab
over 10 years ago
Not able to pull the deadline for a task or process below is the code used.
ServiceContext serviceContext = ServiceLocator.getAdministratorServiceContext();
ProcessExecutionService pes = ServiceLocator.getProcessExecutionService(serviceContext);
LOG.debug(pes.getDeadlineForProcess(processId));
LOG.debug(pes.getDeadlineForTask(taskId));
Regards,
Sarika Bansal...
OriginalPostID-118695
OriginalPostID-118695
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 10 years ago
If you are using a custom servlet plug-in then ignore the line:
ConfigurationLoader.initializeConfigurations();
from my example, you won't need it.
Looking at your stack trace I do not see any reference to your actual servlet plug-in, can you do the following:
1. Stop the application server
2. Delete the application server log (even the native ones outside Appian)
3. Start the application server
4. Reproduce the issue
5. Provide the package of your servlet plug-in
6. Attach the clean application server logs showing the stack trace that actually has references to your servlet plug-in? (all the packages in the stack trace above are Appian related I do not see any reference to your custom class)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 10 years ago
If you are using a custom servlet plug-in then ignore the line:
ConfigurationLoader.initializeConfigurations();
from my example, you won't need it.
Looking at your stack trace I do not see any reference to your actual servlet plug-in, can you do the following:
1. Stop the application server
2. Delete the application server log (even the native ones outside Appian)
3. Start the application server
4. Reproduce the issue
5. Provide the package of your servlet plug-in
6. Attach the clean application server logs showing the stack trace that actually has references to your servlet plug-in? (all the packages in the stack trace above are Appian related I do not see any reference to your custom class)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data