Print this page

Legacy Contract Approvals Function Retiring Spring '15 [[EE, UE Customers]] - FAQs

Knowledge Article Number 000199129
Description

With the Spring ’15 release*, we will retire the legacy Contract Approvals function. This means that after the Spring ’15 release, you will no longer be able to create, approve, or reject Approval requests and the legacy Contract Approvals function will become read-only.

Resolution

Legacy Contract Approvals Function to be Retired [[EE, UE Customers]]

Frequently Asked Questions

1.  What is changing and when?

a. With the Spring ’15 release*, we will retire the legacy Contract Approvals function and it will become read-only. Also, you will no longer be able to create, approve, or reject Approval requests.
b. We encourage you to set up and begin using the Standard Workflow and Approvals feature on the Contracts home page.

*Currently targeted for February 2015; date subject to change

2.  What exactly will happen after the retirement date passes?

a. After the Spring ’15 release*, the legacy Contract Approval function will become read-only. The following items will be removed:
i.  The “New” button on the “Items to Approve” related list on the Contract details page
ii.  The ‘Approve’ and ‘Reject’ action links on the related list
iii. The ‘Approve’ and ‘Reject’ buttons on the Approval Edit page
b. Existing Approval Requests will continue to be displayed in the related approval list, yet the legacy Contract Approvals function will become read-only.
c.  For pending approval requests,  you will no longer be able to add your approve or reject comments on the Approval Edit page.  
d.  API updates to the Approval Request records will no longer be supported or accessible.

3.  What will happen to the data left in the legacy Contract Approvals function?

a. The data in the existing approval request records will be retained and will be accessible to you in read-only mode and cannot be deleted.

4.  Will I be able to access my data after the Spring ’15 release?

a. Yes, your existing data will continue to be displayed in the ‘Items to Approve’ related list in read-only mode but cannot be deleted or removed.

5.  Why are we making this change?

a. We listen to the feedback provided by our customers and constantly review our portfolio to make sure that we are delivering the most value. Our current usage data shows a very small percentage of our customers are using the legacy Contract Approvals function.
b. Given this data, and the customer feedback we’ve received through the IdeaExchange, we are focusing on developing features that best serve our customer community.

6.  What action must I take?

a. Prior to the Spring ’15 release, we recommend that you set up and begin using the Standard Workflow and Approvals feature on the Contracts home page, if you currently use the legacy Contract Approvals function.

7.  How can customers match the capability of the old and new versions?

a. In the Standard Workflow and Approvals feature, you may retain the capability similar to the legacy Contract Approvals function by adding a workflow field update step to the approval process. Adding this workflow field update will automatically set the Contract Status to “In Approval Process.”
b. You can learn more about how to set up Standard Workflow and Approvals in Help and Training by clicking here.

8.  How can I get more information?

a.  If you have additional questions, please reach out to Customer Support by logging a case via the Help & Training portal.




promote demote