Planning

Get Involved. Join the Conversation.

Topic

    Mark Rinaldi
    What's New in 18.09?Answered
    Topic posted September 4, 2018 by Mark RinaldiBronze Crown: 15,000+ Points, last edited September 5, 2018, tagged EPBCS, Integration, Patching, PBCS, Planning, Security, Strategic Modeling, Workforce 
    206 Views, 14 Comments
    Title:
    What's New in 18.09?
    Summary:
    Read the latest What's New Document for Planning & Budgeting
    Content:

    Here we go again... 18.09 is scheduled to hit your Test pods this Friday.  I'm sure you are all aware of the latest What's New document for 18.09 but, on the odd chance you haven't read it yet, here are my points of interest:

    1. Changes to Provisioning Roles - cleaned up unwanted access when previously assigned to a predefined role.  Consultants/partners that were assigned Admin Roles, even when removed, were still granted access to an environment in certain cases. Now, only identity domain users who are assigned to a predefined role (i.e. Service Administrator, Power User, User, and Viewer) can log into an environment.  Only users who are assigned to predefined roles can be added to groups or assigned Read/Write/Execute privileges in Access Control or via EPM Automate commands.  Basically, users need to be assigned to a predefined role for them to be included in features in the product.
    2. New EPM Automate Version that supports addUsers, assignRole, removeUsers, and unassignRole as new commands
    3. REST APIs also support these 4 new operations:  Add/Remove users to and identity domain, Assign/Remove predefined role assignment
    4. As we continue to move away from the old User Interface, Application Settings are now available in the Simplified User Interface (SUI) under the Application\Settings card.
    5. Unified User Preferences across the Planning and Budgeting platform (e.g. PBCS, EPBCS, SWPCS, FCCS, TRCS).  Set the preferences once and it is seamlessly integrated with the other applications.   Go to Home\Tools\User Preferences in the SUI to set your profile picture, select members for user variables, set preferences for ad hoc options and printed reports, etc.
    6. Data Management (DM) supports an Incremental File Adapter - now loading source data files can leverage this Incremental File Adapter to allow DM to identity only the changes between source file uploads and only load the smaller file with the changes.  This DM Incremental File Adapter accounts for all previous loads to always provide the latest changes.  Loading incremental changes only should speed up the data load process.
    7. DM also now supports drilling down from summary members.  In DM, select "Enable Summary Drill" option, set the option Create Drill Region to "Yes," and the Drill icon will be enabled at the summary level.  Drill is limited to 1000 descendant members for a dimension.
    8. Strategic Modeling - the Account Forecast Free-form Formula page now includes an "Apply To" button that pushes down the free-form formula to selected sub-accounts or children of the current account.
    9. Workforce Planning performance enhancements!  We have pulled the FIXPARALLEL and two outer FIX statements out of the Process Loaded Data, Synchronize Definition, and Synchronize Defaults TEMPLATES and created a new Template, OWP_Fix Parallel_T, where the FIXPARALLEL and two outer FIX statements for those templates now exist.  Thus, you can modify the FIXPARALLEL dimension in one spot for all the rules/templates using these templates.  The Add Requisition and Assign Compensation TEMPLATES have also been modified and are used in the OWP_Add Requisition_GT and OWP_Change Requisition_GT TEMPLATES.  The OWP_Plan Departure_T TEMPLATE has also been modified, which is used in the OWP_Plan Departure RULE. 
      • Be sure to Restore any of these modified artifacts to take advantage of the enhancements
      • Be sure to Re-deploy the templates/rules affected by these enhancements
      • See the Updating Workforce Artifacts to Use New Features appendix in the EPBCS Administrator's Guide for more information
      • We also did some general cleanup of nested FIX and IF statements to improve performance in these templates
      • We are finding that the single, biggest change to improve performance on the Process Loaded Data and Synchronize Rules is to set the appropriate dimension in the FIXPARALLEL statement.  We default it to Entity since we don't know if you will create Custom Dimensions.
      • Test with realistic and representative data to identify the best dimension for parallelization

    Upcoming Changes:

    1. Proposed changes to application-level Access Control to improve integration across planning, consolidation and close, tax reporting, and EDMCS applications.  Predefined roles will no longer appear as Groups in Access Control.  This proposed change will NOT affect how you create and manage groups or use them for application-level access control.  If you are concerned with the impact of this change on your environment, please create a Service Request in My Oracle Support explaining your use case.
    2. As I mentioned in an earlier post, the deprecation of the Classic Dimension editor has been deferred until sometime in early CY2019 to allow more time for customers to acclimate to the Simplified Dimension editor.  We will provide at least 2 months notice prior to deprecation.  Please continue use the Simplified Dimension editor and log any bugs or enhancement requests.  Safe Harbor, we are aware of several enhancements and are actively working on them.  You should see improvements in future releases prior to the deprecation of the Classic Dimension editor.
    3. As mentioned several times in previous posts, we have deferred the deprecation for the ability to create new composite forms until early CY2019.

    Please look into the Workforce enhancements and let me know how your performance results vary (improve).

    Enjoy 18.09!

    Best Comment

    Andy Tauro

    Mark,

    Really looking forward to the release. Do you know when we can expect the online REST API document to be updated to reflect the new functions in #3?

    Also, a question on #7, "DM also now supports drilling down from summary members" - will this require loading of dimensions via DM as well, or does this use Planning to determine the children of the member being drilled-down from? Hoping the latter, but wanted to confirm.

    Thanks,

    Andy

    Comment

     

    • Mark Rinaldi

      For early viewers of this post, I modified it to separate which Templates were modified for the FIXPARALLEL Template.  The OWP_Add Requistion_T and OWP_Assign Compensation_T Templates were modified for performance enhancement but NOT related to the FIXPARALLEL and outer 2 FIX statements.\

      Sorry for any confusion.

    • Peter Nitschke

      Going to be an awesome release! 

      As soon as the summary drill is in I'll be writing that up - got a few key customers where we've done some awful hackjobs to make the level-0 drill a little more palatable that this solves. 

      with the incremental load - is there anything that you can share with regard to performance? Definitely be interested to look at some things where we have multi million record transaction loads we've shied away from. 

      p

       

      • Mark Rinaldi

        I've asked the DM team if they have any performance metrics to share.  I will let you know what they say.

        Thanks.

      • Mark Rinaldi

        Good news... Summary Drill uses Planning metadata so no need to load dimensions into DM for this feature.

    • Andy Tauro

      Mark,

      Really looking forward to the release. Do you know when we can expect the online REST API document to be updated to reflect the new functions in #3?

      Also, a question on #7, "DM also now supports drilling down from summary members" - will this require loading of dimensions via DM as well, or does this use Planning to determine the children of the member being drilled-down from? Hoping the latter, but wanted to confirm.

      Thanks,

      Andy

      • Mark Rinaldi

        Whoops, hit the wrong button and have you a "Best Answer" award!  Anyway, I also had a RTFM moment inquiring about your question internally.  The What's New doc has this information in it....

        The Oracle Help Center provides access to updated documentation. The updates will be available in the Help Center on September 7, 2018. Some of the links to new feature documentation included in this document will not work until after the Oracle Help Center update is complete.

      • Mark Rinaldi

        Put this in response to wrong question...

        Good news... Summary Drill uses Planning metadata so no need to load dimensions into DM for this feature.

    • Mark Rinaldi

      Added OWP_Plan Departure_T template and OWP_Plan Departure rule to list of modified artifacts with performance enhancements.   Again, refer to the Admin Guide Appendix for the full list of modified, new, and obsolete artifacts with this enhancement.  The Admin Guide will be updated on 7-Sep.

    • Tuan-Anh M. Nguyen

      2. New EPM Automate Version that supports addUsers, assignRole, removeUsers, and unassignRole as new commands

      A very nice add.  

    • Levent Abik

      2. New EPM Automate Version that supports addUsers, assignRole, removeUsers, and unassignRole as new commands

       

      This is perfect!

    • Andy Tauro

      Has anyone tried the 'addUsers', 'removeUsers', 'assignRole' and 'unassignRole' options via EPMAutomate or REST API? I have run into issues with them, and have an SR going, but wanted to see if others are seeing this behavior or if it is just me (totally fine with that, if someone can tell me what I am doing wrong):

      • addUsers - this works via EPMAutomate, but 'ADD_USERS' via REST API returns 503 - Service is unavailable
      • removeUsers - this works via EPMAutomate, 'REMOVE_USERS' works via REST API
      • assignRole / unassignRole - the documentation says to use 'User' instead of 'Planner', but it fails via EPMAutomate when using 'User', works when using 'Planner'. REST API, ASSIGN_ROLE / UNASSIGN_ROLE fails with '503 - Service is unavailable'

      All this is against the Test instance which has the 18.09 patch.

      • Mark Rinaldi

        Sent you a DM but for others that may be curious....

        You are sending the parameters in a JSON string, which is not expected. Try this...

        def createUsers(parParameters) {
        def url;
        String strJobStatus;
        String strJobLogFile;
        def payload = “filename=”+ parParameters.filename+”&userpassword=”+ parParameters.userPassword + “&resetpassword=”+ parParameters.resetPassword;

        Also, while accessing the API via POSTMAN, you need to send parameters in the request body, not the query string and all the parameters should be lower case

    • Andy Tauro

      Hi Mark,

      In Postman, I did send this via the "Params" functionality and Postman appends it to the URL as seen in the screenshot. I showed this to the Oracle Analyst during a WebEx, typing in the Params by hand and showing the result. Also, I used Postman after I was directed to it by the analyst. In the Groovy code, I am building the payload as a JSON block, and converting the entire block to a string before sending it to REST. The "executeRequest" helper function will not accept a JSON parameter for the 'payload' parameter. I have used this same approach for other calls, such as running AIF jobs with success. I will be happy to walk through this again via WebEx.

      Thanks for the quick response,

      Andy

      • Andy Tauro

        Hi Mark, All,

        I want to point out 2 things that I was doing wrong -

        1) As Mark pointed out, I was building my payload in JSON format, when I should not have, as the documentation does not specify the need for JSON anywhere. I made the incorrect assumption based on the other REST endpoints

        2) The documentation says to use the "keys" in mixed case - userPassword, resetPassword - but it looks like it has to be all lower case instead - userpassword, resetpassword.

        Once I made the change, the REST API calls are working.

        Thanks for bearing with me, and I apologize for the mistakes.

        Andy