GridComponent - Flexibility in Fields Displayed

[Migration User]

I am a new user to the Workflow Solution, and I need some help. I am trying to set up a form where there are multiple detail records being displayed in a GridComponent. I am able to set up the grid to see all of the fields of user interest. My problem is that based on the value of a variable I want to be able to different fields displayed and with a different order. So for example, let's say my variable has the value "04" (at runtime) and I want to dynamically see fields "A", "C", and "E", but when the value is "06" I want to see fields "B", "D", and "H". There will be other values to the variable and different grid displays. The data in the grid must also be editable. I have set up a table which can track fields to be seen and the field order for individual variable values to help dynamically provide information of how to set up the grid. How do I do this? Should I be using a different component instead of GridComponent? Should I create a new grid component? If so, how do I do that? Thank you, DAK_Boy

[Migration User]

DAK_Boy, If I understand your question correctly, you want to display certain values in a GridComponent based on the value of a process variable. If I misunderstood you, please correct me. If I understood you correctly, here's how you do it: Instead of using just one GridComponent and trying to change the values in the individual fields, use two or more GridComponents and layer them on top of each other on your form. Then, in the GridComponent editor (double-click the component to view the editor), define what each GridComponent should display. Click on the "Function" tab, then configure the "Visible" property using a dynamic model. Use the dynamic model to evaluate the determinative process variable that defines which GridComponent should be displayed. Configure the other GridComponents in the same way. To get the dynamic models to set one of the GridComponenet's visibility property to "true" or "false," use a rule component(s) and two end components set to opposite values. For example, you use the values "04" and "06" in your question. These are your determinative process variables. In the dynamic model of the GridComponent that corresponds with the value "04," use a "Matches" rule component. Compare your determinative process variable with "04." Then, use two end components - one with a mapping value set to "True" and the other set to "False." Point the "04" outcome path to true, and the "nomatch" outcome path to false. Set the other GridComponent(s) in the same way, so that only one GridComponent appears on the form at runtime. I wrote a larger article for the main Workflow Juice site on your question that should appear in a day or two. It is more thorough and includes screenshots. Does this help? -Stuper

[Migration User]

Thank you for your response. Since there will probably be more than 10 variations, the overhead of having so many GridComponents would make the form huge and also difficult to edit.

I am looking for something that is more dynamic. I have created a ColumnVisibility table which can track the fields to be displayed and associated with a process variable's value (an Invoice Type). Each record has the Invoice Type value, the column name, a visibility flag, column order number, and a required flag.

Using the process variable's value(Invoice Type), the set of records ColumnVisibility is read for that view. I want to use this set of records to determine the field visibility and order in the GridComponent. This process will make the grid display more dynamic.
This is the situation that I am looking at.

[Migration User]

As this saga continues... In Visual Studio, I am using C# to create my own type of GridComponent class (GridComponentABC) by deriving it from the actual GridComponent.

At this moment I am having problems getting the Form (in the FormBuilder) to make use of GridComponentABC because I am not setting up the IFormComponentRenderer correctly. As a result, I cannot even edit this new grid component to set up the configuration. The GridComponent class definition hides what is being done to create the correct Renderer class.

Any ideas?

Thanks, DAK_Boy

[Migration User]

Have you had a look at the component developer guide? Building UI Components for the Web Form builder is the most sophisticated concept in Workflow Solution Development because the API actually requires 3 classes: 1. A class that defines your controls properties and passes them between the design time and runtime representation 2. A design time representation 3. a runtime representation. If you've not seen this document it might help you a lot. Another option would be to use an iFrame or something to embed your dynamic grid in the web form without it being a form control in the official sense. The WebForm editors grid control that exsts obviously doesn't support the dynamic reconfiguration that you're trying to do, and I'm sorry for that! stuper