search cancel

Budget Plan creation: "Submit Option" is set to "Merge" even when the default is set to "Replace" in New UI

book

Article ID: 142388

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

In the Modern User Experience (UX / UI), when creating a budget plan, the submit option is set to merge even when the default is set to Replace.

Steps to Reproduce:

  1. Navigate to the Cost Plan object (Administration -> Objects -> {Cost Plan})
  2. Open the "Submit Option" attribute
  3. Set the "Default" field to "Replace"
  4. In Classic PPM, create a new project (Home -> Projects)
  5. Provide Department and Location to the newly created project ({Project} -> Settings {Sub page})
  6. Create a new Cost Plan ({Project} -> Financial Plans {tab})
  7. Submit the newly created Cost Plan for approval as budget plan (Actions {from Cost Plan list view} -> Submit Plan of Record for approval)
  8. Provide a Plan ID in the "Submit For Approval" page
  9. Navigate to submitted Budget Plan and approve it (Budget Plans {sub page})
  10. Navigate back to the Cost Plans sub page. Create a new Cost Plan and submit it for approval again, as in Step 7
  11. Notice that the "Submit Option" field is set to "Replace"
  12. Now open the same project in the New UI
  13. Navigate to the Financials tab
  14. Display the List view by selecting the icon from the top left corner of the page
  15. Submit the Plan of Record for approval
  16. Notice that the "Submit Option" field is set to "Merge"

Expected Result: In Step 16, the "Submit Option" field is defaulted to "Replace"
Actual Result: In Step 16, the "Submit Option" field is set to "Merge"

Cause

Due to Defect ID DE52475.

Environment

Version: 15.7.1

Resolution

Fixed in 15.8.