Version manager in HXM Workforce Planning

[zwerum]

Hi,

while exploring the HXM content, another question popped into my head:

From the business point of view, it is important to store different versions during different project phases as a "snapshot" or planning milestone, which means that more versions are needed than those stored in the model.

The input forms in the HXM content are embedded in an application. Since there is no story with input forms, is it possible to open the version manager in the application? Or is it possible to create a new version directly in the model?

I couldn't find either way and a workaround with creating an input story just to add a new version in the version manager is pretty inconvenient.

Thanks in advance for your help!

Zoe

[Michael_Fox · Accepted solution]

Hello again zwerum 🙂

There are a couple options for you. One is to use the Table Actions while running the app to open the Table in a New Story. Then you will have full capability to do as you wish without first having to create story from scratch, choose data model, setup table, etc.

The other option is to enable Version Management within the app. I have detailed the steps to do this in the attached screenshots. First you will need to open the app in Edit Mode, and change Styling on the table to enable Version Copy/Delete (first screenshot). Then Save and Run the app. You will then be able to create/delete Private Versions within the context of a cell on the table (second screenshot), AND you will have full Version Management capability with the pop-up toolbar above the Home button (third screenshot - just hover directly above the Home button).

Hope this helps!

[zwerum · Accepted solution]

Thank you for your quick answer! This helps a lot!

[zwerum · Accepted solution]

Hello michael.fox3,

apologies for bothering again but I have additional questions regarding versions in the HXM content:

I found this process flow on signavio for the first planning step "Prepare Plan Cycle". The preparation includes the data import. How do you import the version? In the predefined model there are only the versions "Financial Plan" and "HXM" but not the version "Strategic Business Goals".

Furthermore, the steps "initialize baseline version" and "unlock baseline version" contain privat versions. How should these steps be performed if the version manager is not set as default?

Thanks in advance!

Zoe

[Michael_Fox]

Hi zwerum - The initializing and version references reflected in the Process Documentation is already built into the standard content we provide. For example, when using the Configuration app, our scripts will seed and initialize the versions through the scripts that get executed as the user interacts with the app (see screenshot: initialize.png).

I need to follow up with the development team regarding the labels in the documentation and whether we really have "Private" and "Public" versions when interacting with our standard content or if we only have "Public" versions that we put in Edit Mode, and then publish / revert the changes.

Your prior input about Version Management not being exposed by default has already been entered as an enhancement request for consideration in a future release.

Regarding the Strategic Business Goals, we do not yet have business content that covers that planning process, and thus we have not yet provided such a version out of the box in this content. That would need to be configured on your end.

Thanks, Mike

initialize.png

[zwerum]

Thank you for checking with the development team!

The concept with the private versions in the process flow does make sense to me, especially considering the collaboration functionalities (private versions can be shared, reviewed, discussed and approved before publishing).

But even if I copy the aggegated plan version into a privat version and try to work with the privat version, deleting the version filter from the application and integrating an input control for versions, I can't see data when running the application:

This is because the aggregated version is set as a default in the script.

To enhance the whole issue with the versions I created the following improvement request:

Improvement Request Details - Customer Influence (sap.com)

[Michael_Fox]

Thanks for submitting the improvement request! dominik.fischer02 - I've assigned you to the improvement request in the Ideas portal.

Thanks, Mike

[zwerum]

Hi michael.fox3!

Apologies for not giving peace to this topic and thank you for all the time and effort you are putting in.

However, I re-read your comment and I think all (or most of) the issues I'm having with versions are based on a bug. So I would like to make sure that I understood your comment correctly:

"The initializing and version references reflected in the Process Documentation is already built into the standard content we provide. For example, when using the Configuration app, our scripts will seed and initialize the versions through the scripts that get executed as the user interacts with the app (see screenshot: initialize.png)."

Does this mean that the version I select and initiate in the Configuration application is automatically selected as the planning version in the other applications (such as Aggregated Internal HC Plan or Aggregated External HC Plan)?

Because this is currently not the case. Here is an example with a public version I created called "Baseline" (but the same case is with all other existing versions beside the version "Aggregated_Plan"):

Example:

I set up the desired version, copied no data (selected manual) because the version is already a copy of aggregated plan and initialised the version (see screenshot).

In the Model the version category is "Planning", it is visible, the planning direction is "aggregated" and the plan level is "P3". So all fields are simular to the version "Aggregated_Plan".

But when I go back to the Overview and select "Aggregated Internal HC Plan", the selected version is still "Aggregated_Plan" and did not change to the version I initialised / published:

I hope after clarifying this I do not have to bother you with versions in HXM anymore...

[rudolf_lindt]

Hello zwerum,

thanks for reaching out!

In order for your applications to initialize with your new version (which in your case is "Baseline"), please enter the Aggregated Internal HC Plan or the Aggregated External HC Plan application in edit mode first.

Please scroll down to the Script Variables and enter as your default value for the cfg_planVersion variable your version name, which should be public.Baseline.

Alternatively you can also jump into the getCustomizing script. It contains a line which looks like this:

Simply set the variable inside the script to your new version and save your application. Please note that this line will only work if there is no default value set for your cfg_planVersion variable (this is the case when the Default Value field shown in the first image is blank).

As a third and more dynamic option, you can also change the version by modifying your link to the application. Simply add "&p_cfg_planVersion=public.Baseline" at the end of your link in order to initialize the analytic application with your new version. Your link should look like this:

https://<YourTenant>/<YourAppID>/?p_toggleIsPredictiveEnabled=true&p_cfg_planVersion=public.Baseline

Now, the table should initialize correctly. Let us know if that solved your issue!

Thanks a lot and kind regards

Rudi

[zwerum]

Thanks Rudi!

It is working and helps a lot! It still doesn't replace my improvement request for a more user friendly handling, but for now this is a good work around.

Thank you for your fast answer and your comprehensive description.

Zoe