Add "Data Entry Dialog" as procedure action

Nico Weber
Nico Weber Active Partner, Community Captain
Second Anniversary 25 Likes 25 Up Votes 10 Comments

1. What is your idea?
I propose adding a "Data Entry Dialog" procedure action to enable the opening of a "Data Entry Dialog" during procedure execution. This would allow users to input values directly within a procedure logic/workflow.

2. What specific problem are you trying to find a solution to, or what new scenario would this idea respond to?
Currently, when users need to input values — such as sales data for a new customer combination during a planning process — we have to create a DataView with a cube containing a dimension with just one dummy element, like "entry dummy". This setup is used to "simulate" a data entry field and the entered value is then processed through a procedure.

By introducing a "Data Entry Dialog" as a procedure action, users could enter a value directly in a dialog opened from procedure logic/workflow. The value would be temporarily stored and directly processed in the subsequent procedure logic/workflow.

6
6 votes

Open For Voting · Last Updated

Comments

  • Sergi Fernández
    Sergi Fernández Active Partner, Community Captain
    100 Up Votes 10 Comments Second Anniversary 5 Likes

    Interesting @Nico Weber. I think it'd be a great addition to Board.
    I just want to add that it might be a good idea to combine this with the use of temporary cubes, as it would simplify some tasks for the developers.

  • Hi @Nico Weber,
    i like that Idea of having a more "Workflow-Like"-approach directly within a procedure.

    I am currently thinking, if "a Data Entry Dialog" in procedures would also be a good way of creating new entity members in e.g. Planning Applications. In some planning cases the planner hat to create new Entity Elements first before entering a value. So if a new feature would also cover that, it would be also possible to lead the planner through a complete process of creating new elements and directly also enter a value for that, which is then processed in the following procedure logic.

    What do you think?

    Best regards,
    Fabian