Advanced show page action for usage in microflows.

20

Idea: Advanced show page action
Instead of the regular show page I'm looking for a seperate but more advanced show page action, that will hopefully give a lot of flexibility.

The idea goes as followed:

It basically consists of 2 parts:
An action to call the page with advanced settings.
An action to trigger data loading in the microflow that calls the page.

The page being called opens with "temp data / placeholder entities" till the real data is available.
If real data is still being loaded because it was not directly available from the microflow that calls the page, the section allows for setting a pre-loader, preferably in .svg or .gif format. This will be the case when a datasource microflow was selected. (More on this below).

The page can be built with regular view/lists/grids/template grids etc identifiable by their "name" attributes.

As the datasource for the view elements you can use the "Caller of page microflow"

All views and lists in the called page display the following: 
"Caller of the page microflow_name, {%Datasource microflow name / Output object / Output list of objects%}, caller of the page"

instead of
"Object, caller of the page"

When right clicking the view or lists add a few navigation options:
"Go to caller of the page microflow"
"Go to view / list source microflow or entity"
"Select microflow"
"Select entity"

Using this advanced page call action you can still use the

"Set page title" like the regular page call action.
But please also add the possibility to use attribute content from the entities in this title.

"Set parameters per view / list / grid / template grid"

For each view/list/grid in the layout of the page that is being called. Allow for setting a few parameters.

Within the page there is ofcourse a parent > child relation, this should be visible in this configuration of the page action call.
So when i have a top level view and that contains a grid, make it visually clear that the grid is part of the view.
 ​
Parameters that are available in my mind have to be the following:

• Select the Object(s) to pass (a single object or object list from the microflow calling the page (note that database/association/xpath retrieve lists can be already loaded in the page calling microflow too) or a seperate datasource microflow source, restricted that these microflows can't contain other page calls or close pages) the output of the datasource microflow is what is being used to fill
  If the datasource is a microflow.
  - Set pre-loader .gif or .svg for microflow (Should be required and have a default pre-loader)
  - Asynchronous loading OFF (when it is off, the datasource microflow for this view/list or grid will be triggered once the page is being shown)
  - Asynchronous loading ON (This microflow is available to use in the new "Trigger data loading" action described above, you can place this trigger in the caller of page microflow, what this does is that it runs the datasource microflow for this view in the background, so perhaps you need to call a webservice or whatever to get data, while this microflow is still running the pre-loader animation is displayed) But this will allow you to start loading data for the view before the page is being displayed.
  
  When the Object type that is used as the datasource has specializations these should be selectable.
  So that when the view or list is displayed you can choose how to display the object into the view / list, either as specialization or the datasource entity.
• Select or create new snippet to use for the display of the datasource object(s) when it is an entity view / list view / template grid. 
  If the returned object from the datasource microflow or used objects from the call page microflow have specializations in the database. Allow for selecting / creating a seperate snippet for each specialization.
• Set empty text (displayed when no entity was passed as parameter or returned from the microflow.
• Select display section from the page layout (This overwrites the way views are placed within the layout) (For example: I have 4 sections in my layout template I want to be able to select the section in which to display the view / list, this can only be done for parent views/lists/grids refererring to the page structuring) I can imagine this being sort of a drag and drop system where you can drag the "view name" to a part of the layout.

 

"Wait with showing page till all data is loaded" boolean, this prevents the page from opening till all underlying data is loaded including the datasource microflows. Enabling this should disable the pre-loaders in the datasource microflows. 

asked 2016-10-14

0 answers