Proposal Update API Requires Proposal ID As Mandatory Field, Unable to View Proposal in UI After API Update in Instantis EnterpriseTrack (Doc ID 2172312.1)

Last updated on OCTOBER 12, 2016

Applies to:

Instantis EnterpriseTrack Cloud Service - Version 16.1.1.0 and later
Instantis EnterpriseTrack - Version 16.1.1.0 and later
Information in this document applies to any platform.

Symptoms

1. Upgrade to version 16.1.1.0 from version 16.1.0.0 now requires both the Proposal Name and Proposal ID to be passed with Proposal create and update to pass accepted information in an environment.
    Whereas in version 16.1.0.0 Proposal Name was the only field being used to update information in an environment.

2. Proposals updated with an API Update function are not accessible to view, able to be edited, and require log out of User Interface to proceed.


STEPS to determine if API Update not working for Proposal Name only
-----------------------
The issue can be reproduced at will with the following steps:

  1. Download Template for Update Proposal
  2. Locate an existing Proposal, enter that name in the proposal name field
  3. Edit text in any section allowable.
  4. Run API
  5. Results:
{"global_properties": {"char_set": "UTF-8","date_format": "MMM/dd/yyyy","language": "en","api_version": "16.1"},"response_data": {"request_type": "update","entity_type": "proposal","response_code": "9999","response_desc": "Internal Error: hasAccess: mvcount() = 0"},"app_data": {}}


Steps to determine if API Update working when using Proposal Name and ID, Proposal is not accessible, editable and causes log out:
-----------------------
After running a successful API UPDATE for Proposal, to verify in the system the following results happen:


1. log in as Administrative user, navigate to proposals
2. See "CANNOT DOWNLOAD THIS DATA PART!"
3. Go to Advanced Search
4. select ALL Proposal Status' Click Search
5. Text search in Proposal name field for appropriate text if additional filtering is needed to locate proposal quickly.
6. Click on the name of the proposal updated with the API template.
     Submission failed.<br> INTERNAL_ERROR: isFinTemplateElementEnabled Incorrect fin element: savings for finance template: defaultGlobalFinTemplateID and Version: <<environment specific>>
7. Click Back
8. Click Proposal ID for the proposal that was updated with the API
     Submission failed.<br> INTERNAL_ERROR: isFinTemplateElementEnabled Incorrect fin element: savings for finance template: defaultGlobalFinTemplateID and Version: <<environment specific>>
9. Click Back
10. Use Action Drop Down, "View Details"
     Submission failed.<br> INTERNAL_ERROR: isFinTemplateElementEnabled Incorrect fin element: savings for finance template: defaultGlobalFinTemplateID and Version: <<environment specific>>
11. Click Back
12. Use Action Drop Down, "Edit" > "Details"
13. Navigate to section that was updated with the API - Notice Data is accurately placed.
14. Click Cancel
     Submission failed.<br> INTERNAL_ERROR: isFinTemplateElementEnabled Incorrect fin element: savings for finance template: defaultGlobalFinTemplateID and Version: <<environment specific>>
15. Click Back
16. Type something to test an update in a field. Click Save
     Submission failed.<br> INTERNAL_ERROR: isFinTemplateElementEnabled Incorrect fin element: savings for finance template: defaultGlobalFinTemplateID and Version: <<environment specific>>
NOTE: THERE IS NO WAY TO EXIT the Project Candidate without logging out of the system.



Changes

  1. Upgrade to environment version 16.1.1.0.
  2. Use API Update Proposal to successfully update a proposal with use of Proposal Name and Proposal ID.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms