BPM, Workflow, and Case

Hi

When I create a "Property Table" on the views,  I need to set it with Multivalue (Multiple Values) properties. But I dont know why the dates shows as required fields when I did not set up them as "Required" .

Is there any way for those not to show with the asterix as required?



I also checked on the "Case Type" properties and are not "required"


Any idea on how not to turn it required?

Regards

------------------------------
Martin Iturbide
Consultant
Next Step C.A.
Quito
------------------------------

Hi Martin. Looks like your use case is to create a table where you can add rows of similar data to the case.

The approach you are using is a much older style where we used the CPE multi-value prop in a creative way to try and align multiple into a table (columns/rows) and use UI to keep all the participating MV props in sync. While this worked for the most part and allowed basic tables for case properties, it had several limitations as you have found.

The first is that the CPE does not allow null entries in a MVP for certain data types (eg date/number) and that is what is causing the column to become required. Another is that the resulting data is still stored as individual MV prop values that really don't have any data model relationship to the other columns you include in the UI table.

The new approach that was added back around 2015 was a new case/CPE data type called a business object (BO). This object can be defined in Case Builder and represents a multi-value structure that can then be repeated in a UI table.

For example, a case BO can be defined for something like "Dependant" and that would contain SINGLE VALUE props such as Name, Age, etc. You then create a case property called "Dependents" of type Business Object and select "Dependant" as the BO type.

When this property is added to either a classic property view or the newer Client-side Human Service UI pages, it will be rendered as a table of those BO columns and you can add any number of rows.

With this approach, the use of Required is back in your control as it should be.

------------------------------
DAVE PERMAN
------------------------------

Original Message:
Sent: Mon January 23, 2023 04:26 PM
From: Martin Iturbide
Subject: BAW - Property Table show Dates as Mandatory Fields

Hi

When I create a "Property Table" on the views,  I need to set it with Multivalue (Multiple Values) properties. But I dont know why the dates shows as required fields when I did not set up them as "Required" .

Is there any way for those not to show with the asterix as required?



I also checked on the "Case Type" properties and are not "required"


Any idea on how not to turn it required?

Regards

------------------------------
Martin Iturbide
Consultant
Next Step C.A.
Quito
------------------------------

Thanks a lot Dave. I did a quick exercise with Business Object (BO) and the dates no longer shows as mandatory. I will make more exercises to use more BO instead of the common "Property Table".

If you found any documentation that you found relevant when learning Business Object (BO), I will appreciate any links.

Regards

------------------------------
Martin Iturbide
Consultant
Next Step C.A.
Quito
------------------------------

Original Message:
Sent: Wed January 25, 2023 02:11 PM
From: DAVE PERMAN
Subject: BAW - Property Table show Dates as Mandatory Fields

Hi Martin. Looks like your use case is to create a table where you can add rows of similar data to the case.

The approach you are using is a much older style where we used the CPE multi-value prop in a creative way to try and align multiple into a table (columns/rows) and use UI to keep all the participating MV props in sync. While this worked for the most part and allowed basic tables for case properties, it had several limitations as you have found.

The first is that the CPE does not allow null entries in a MVP for certain data types (eg date/number) and that is what is causing the column to become required. Another is that the resulting data is still stored as individual MV prop values that really don't have any data model relationship to the other columns you include in the UI table.

The new approach that was added back around 2015 was a new case/CPE data type called a business object (BO). This object can be defined in Case Builder and represents a multi-value structure that can then be repeated in a UI table.

For example, a case BO can be defined for something like "Dependant" and that would contain SINGLE VALUE props such as Name, Age, etc. You then create a case property called "Dependents" of type Business Object and select "Dependant" as the BO type.

When this property is added to either a classic property view or the newer Client-side Human Service UI pages, it will be rendered as a table of those BO columns and you can add any number of rows.

With this approach, the use of Required is back in your control as it should be.

------------------------------
DAVE PERMAN

Original Message:
Sent: Mon January 23, 2023 04:26 PM
From: Martin Iturbide
Subject: BAW - Property Table show Dates as Mandatory Fields

Hi

When I create a "Property Table" on the views,  I need to set it with Multivalue (Multiple Values) properties. But I dont know why the dates shows as required fields when I did not set up them as "Required" .

Is there any way for those not to show with the asterix as required?



I also checked on the "Case Type" properties and are not "required"


Any idea on how not to turn it required?

Regards

------------------------------
Martin Iturbide
Consultant
Next Step C.A.
Quito
------------------------------