Uber form grid control Hot

by Scott Hofmann on June 11, 2015

Provide single form grid control that offers the features of the SBM REST Grid, and Relational Grid such that is can display internal SBM data and external data from REST service, SOAP web service or ODBC (SQL).

  • If a single grid control was provided that displays both internal SBM data and external non-SBM data delivered via REST, SOAP or ODBC (SQL), the end-users would benefit from a more consistent user interface regardless of the data source.

    The current SBM grid or multi-row selection controls have limitations that result in the need to utilize multiple grid and list controls in a single given process application. The internal or external data limitations are as follows:
    1) Multi-relational Field (MRF) - displays internal Primary or Aux table SBM data only.  
    2) Single-relational Field (SRF) - displays internal  Primary or Aux table SBM data only.  
    3) Multi-Selection Field (MSF) - displays internal SBM application workflow data only.  
    4) Single-Selection Field (SSF) - displays internal SBM application workflow data only.  
    5) Relational Grid - displays internal Primary or Aux table SBM data only.
    6) SBM REST Grid - displays data external to SBM.

    Many new SBM users struggle with the user interface conventions of the MRF, SRF, MSF, SSF. End-Users cannot remember how to search, use the lookup, update or create records features for these fields types. Relational Grid and SBM REST Grid offer multi-column sorting and other advance display features that are improvements over the MRF, SRF, MSF, and SSF fields.

    The single grid control should support the following non-comprehensive list of features:
    1) displays multiple sortable columns much like a list report.
    2) allows for design-time and run-time selection of displayable columns. (The case for run time displayable columns is to allow end-users the ability to better fit the grid to their screen. A good example is how the SBM REST grid currently displays the RM Run Report service. The REST service may return 15 columns but the end user may only need to view the 1st column, 3rd column, and the 15th column. The REST grid will expand to the right forcing the user to horizontal slide the form back and forth to view the results they want to view.)
    3) Allows the end-user to select 1 or more items within the control within a transition.
    4) Display the end-user's selection in a way that it may be easily for the end-user to view and edit their selection as many times as needed for them to achieve their desired selection.
    5) Iteration of the end-user's selection within Orchestration Steps, JavaScript or AppScript must be possible and easy. Specifically, support the ability to
    •    Iterate through selected items via JavaScript in custom state or transition form.  
    •    Iterate through the values selected via AppScript or Orchestration Steps during a transition OR the form control must allow saving of selected items in a MRF type field (since an MRF can be iterated through via an AppScript or Orchestration Steps)
    6) Display SBM system table data (i.e. data contained within system tables such as TS_AGILE_BACKLOGS which contains the Rank for the records in a given Workcenter Backlog )
    7) Supports a mechanism to retrieve 1000’s of records and provide user feedback while the data is being retrieved and allow user interaction with the control while the data is being retrieved. (i.e. utilization of server side pagination )
    8) Supports a search mechanism to search the records that are contained within the control.
    9) Supports a means of paginating the data displayed within the control.
    10) Supports a means to cite titles for columns based on ordinal column positions (in order to abstract the return dataset from the display).
    11) Ability to alter REST dataset prior to display in REST Grid (See enhancement request)


    Altering the SBM REST Grid to perform tasks that the Relational Grid and the MRF and SRF provide seems like the easiest path.

    Ideas

    Status
    Target Release
    11.2
  • Please login to view any attachments.

  • Already have an account? or Create an account
    Many of these items have been delivered. Ideas need to contain one idea so that they can be tracked, resolved and closed individually. I'm marking this idea as delivered but if there is anything that was not properly delivered, please submit a new idea.
    David J. Easter Commented by David J. Easter February 14, 2017
    #1 Reviewer  -  

    Many of these items have been delivered. Ideas need to contain one idea so that they can be tracked, resolved and closed individually. I'm marking this idea as delivered but if there is anything that was not properly delivered, please submit a new idea.

    Hi Scott,

    FYI, the only changes revelant to this idea that we've made in SBM 11.0 are related to the REST Grid Widget. We have not changed or added functionality to single and multi relational and selection fields. The Relational Grid is also unchanged and can display and update only single and multi-relational fields.

    Here are responses to your questions, in so far as they relate to the REST Grid Widget.

    1) Displays multiple sortable columns much like a list report
    -->Already supported prior to SBM 11.0.

    2) allows for design-time and run-time selection of displayable columns.
    -->Design-time selection was already supported. Dynamic (end-user) selection available in SBM 11.0.

    3) Allows the end-user to select 1 or more items within the control within a transition.
    -->Already supported prior to SBM 11.0.

    4) Display the end-user's selection in a way that it may be easily for the end-user to view and edit their selection as many times as needed for them to achieve their desired selection.
    -->No changes to the way REST Grid handles selection. Checkbox and row selection are supported. Depending on REST Service, querying to limit result set is available.

    5) Iteration of the end-user's selection within Orchestration Steps, JavaScript or AppScript must be possible and easy.
    -->Already supported prior to SBM 11.0 using the RESTGrid.resultList property. Orchestration and AppScript operate only on item data, so since REST Results are transient, this cannot be done without moving the selection information into the item itself.

    6) Display SBM system table data
    -->REST access to system tables is not supported in SBM 11.0.

    7) Supports a mechanism to retrieve 1000’s of records and provide user feedback while the data is being retrieved and allow user interaction with the control while the data is being retrieved. (i.e. utilization of server side pagination )
    -->Client side pagination is supported in SBM 11.0.

    9) Supports a means of paginating the data displayed within the control.
    -->Server side pagination was already supported prior to SBM 11.0.
    -->Client side pagination is supported in SBM 11.0.

    10) Support a means to cite titles for columns based on ordinal column positions (in order to abstract the return dataset from the display).
    -->Column header naming was already supported prior to SBM 11.0.
    -->In SBM 11.0 The ability to alter the REST data prior to display allows mapping of result set data into the expected format so if the REST Service returns a different structure, it can be modified to match the expected structure. See http://www.serenacentral.com/blogs/entry/composer-11-0-modifying-rest-data-before-it-is-rendered

    11) Ability to alter REST dataset prior to display in REST Grid (See enhancement request)
    -->Supported as of SBM 11.0. See http://www.serenacentral.com/blogs/entry/composer-11-0-modifying-rest-data-before-it-is-rendered

    Tom
    Tom Clement Commented by Tom Clement October 30, 2015
    Top 10 Reviewer  -  

    Hi Scott,

    FYI, the only changes revelant to this idea that we've made in SBM 11.0 are related to the REST Grid Widget. We have not changed or added functionality to single and multi relational and selection fields. The Relational Grid is also unchanged and can display and update only single and multi-relational fields.

    Here are responses to your questions, in so far as they relate to the REST Grid Widget.

    1) Displays multiple sortable columns much like a list report
    -->Already supported prior to SBM 11.0.

    2) allows for design-time and run-time selection of displayable columns.
    -->Design-time selection was already supported. Dynamic (end-user) selection available in SBM 11.0.

    3) Allows the end-user to select 1 or more items within the control within a transition.
    -->Already supported prior to SBM 11.0.

    4) Display the end-user's selection in a way that it may be easily for the end-user to view and edit their selection as many times as needed for them to achieve their desired selection.
    -->No changes to the way REST Grid handles selection. Checkbox and row selection are supported. Depending on REST Service, querying to limit result set is available.

    5) Iteration of the end-user's selection within Orchestration Steps, JavaScript or AppScript must be possible and easy.
    -->Already supported prior to SBM 11.0 using the RESTGrid.resultList property. Orchestration and AppScript operate only on item data, so since REST Results are transient, this cannot be done without moving the selection information into the item itself.

    6) Display SBM system table data
    -->REST access to system tables is not supported in SBM 11.0.

    7) Supports a mechanism to retrieve 1000’s of records and provide user feedback while the data is being retrieved and allow user interaction with the control while the data is being retrieved. (i.e. utilization of server side pagination )
    -->Client side pagination is supported in SBM 11.0.

    9) Supports a means of paginating the data displayed within the control.
    -->Server side pagination was already supported prior to SBM 11.0.
    -->Client side pagination is supported in SBM 11.0.

    10) Support a means to cite titles for columns based on ordinal column positions (in order to abstract the return dataset from the display).
    -->Column header naming was already supported prior to SBM 11.0.
    -->In SBM 11.0 The ability to alter the REST data prior to display allows mapping of result set data into the expected format so if the REST Service returns a different structure, it can be modified to match the expected structure. See http://www.serenacentral.com/blogs/entry/composer-11-0-modifying-rest-data-before-it-is-rendered

    11) Ability to alter REST dataset prior to display in REST Grid (See enhancement request)
    -->Supported as of SBM 11.0. See http://www.serenacentral.com/blogs/entry/composer-11-0-modifying-rest-data-before-it-is-rendered

    Tom

    It's always tough to respond to an idea with 11(!) requests in it, but I'll try to group some together.

    Already Offered
    • Allow the end-user to select 1 or more items within the control within a transition.
    • Ability to alter REST dataset prior to display in REST Grid

    Under Consideration for SBM 11.0 (2HCY’15) release
    • Support a mechanism to retrieve 1000’s of records and provide user feedback while the data is being retrieved and allow user interaction with the control while the data is being retrieved.
    o Note: Implementation will be client-side pagination, not server-side due to performance concerns.
    • Support a means to cite titles for columns based on ordinal column positions (in order to abstract the return dataset from the display).

    Under Consideration for 1HCY’16
    • Display multiple sortable columns much like a list report.
    • allow for design-time and run-time selection of displayable columns.
    • Display SBM system table data (i.e. data contained within system tables such as TS_AGILE_BACKLOGS which contains the Rank for the records in a given Workcenter Backlog )
    • Support a search mechanism to search the records that are contained within the control.
    • Support a means of paginating the data displayed within the control.

    Under Consideration for 2HCY’16
    • Iteration of the end-user's selection within Orchestration Steps, JavaScript or AppScript must be possible and easy.

    Active (still in discussion)
    • Display the end-user's selection in a way that it may be easily for the end-user to view and edit their selection as many times as needed for them to achieve their desired selection.
    o Note: we still need to understand the user story behind this request. If you have some examples you could share with us in the comments, we’d appreciate it!

    Since most of these issues are Under Consideration, I will change the status to reflect that.
    David J. Easter Commented by David J. Easter August 07, 2015
    Last updated: August 07, 2015
    #1 Reviewer  -  

    It's always tough to respond to an idea with 11(!) requests in it, but I'll try to group some together.

    Already Offered
    • Allow the end-user to select 1 or more items within the control within a transition.
    • Ability to alter REST dataset prior to display in REST Grid

    Under Consideration for SBM 11.0 (2HCY’15) release
    • Support a mechanism to retrieve 1000’s of records and provide user feedback while the data is being retrieved and allow user interaction with the control while the data is being retrieved.
    o Note: Implementation will be client-side pagination, not server-side due to performance concerns.
    • Support a means to cite titles for columns based on ordinal column positions (in order to abstract the return dataset from the display).

    Under Consideration for 1HCY’16
    • Display multiple sortable columns much like a list report.
    • allow for design-time and run-time selection of displayable columns.
    • Display SBM system table data (i.e. data contained within system tables such as TS_AGILE_BACKLOGS which contains the Rank for the records in a given Workcenter Backlog )
    • Support a search mechanism to search the records that are contained within the control.
    • Support a means of paginating the data displayed within the control.

    Under Consideration for 2HCY’16
    • Iteration of the end-user's selection within Orchestration Steps, JavaScript or AppScript must be possible and easy.

    Active (still in discussion)
    • Display the end-user's selection in a way that it may be easily for the end-user to view and edit their selection as many times as needed for them to achieve their desired selection.
    o Note: we still need to understand the user story behind this request. If you have some examples you could share with us in the comments, we’d appreciate it!

    Since most of these issues are Under Consideration, I will change the status to reflect that.

     

PrintEmail

Recent Tweets