Closed as fixed if next.
The issue here is the Planned Start = Planned End whenever one of the fields is changed. If you change one and the other field snaps to whatever value was populated on the other field.
Retiring the WFs below resolves the issue: triProject - Synchronous - On Change Planned End Date triProject - Synchronous - On Change Planned Start Date
On Facility Project, When Planned Start Date has a vaule should not map the Planned End Date in the Planned Start Date. Fixed WF Onchange Planned End Date issue was the WorkFlow switch was checking against Actual Start Date should be Planned Start Date.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.