BOPF Custom Node - Field Control Not working

[Utrivedi]

Hello,

I have added a custom node under EHHSS_INCIDENT business object. The fields from Custom node need to be dynamic on FPM Layer. So, Field Control configuration has been created based on the Incident Group.

However, this configuration is not even triggered. During the debug, I could see when it fetched the list of Field Control properties, it's in the list; but do not see this Z class being triggered. Anything we are missing here?

Regards,

Udit

[michaelf_]

Hi Udit,

when creating a custom node in BOPF for the EHHSS_INCIDENT object (or any other EHS-object), you have to make sure that you add the determination SET_PROPERTIES to this custom node. This determination uses a generic class to read the applicable field control profiles from the customizing. The details (class, timepoints, triggers, etc.) on this determination can be found in any other node in the incident object (e. g. BASIC_INFO_ALL).

In BOBX (or the tool you're using to add the custom node), you can right-click on the node, choose Create, then Determination.

With kind regards,

Michael

[Utrivedi]

Hello michaelf. ,

Thank you for your comment. I just added the SET_PROPERTIES determination, and the determination is being triggered now. However, its only being triggered called for the first time when the node fields are loaded. It's not being called on any event changes or even when we switch tabs.

Also, there are 2 checkboxes which got checked automatically, and I can't uncheck them even in edit mode(Guided Procedures). What are they? Attached for your reference.

Regards,

Udit

[michaelf_]

Hi Udit,

that's indeed a strange/tricky one!

I would recommend to check the following things:

• Set an external break-point into the field control class (the one of the determination). Check if it striggered for your custom node.
• Set an external break-point into the function class used in the field control profile and validate whether the return is filled correctly. (if applicable)
• If you are using a FBI View for your Form or List UIBB (configured in the feeder class parameters within the component configuration), validate whether the checkbox No Properties is unchecked.

With kind regards,

Michael

[michaelf_]

Hi Udit,

please check the tabs Request, Read & Write Nodes, Node Category Assignment, and Determination Dependency. Make sure that you have selected the corresponding nodes.

If you have a logic in the field control which reacts to a certain field, e. g. if someone picked yes, another field becomes visible/mandatory, you have to make sure that this field change fires an event in the component configuration of FPM (FBI_DEFAULT).

With kind regards,

Michael

[Utrivedi]

Hi Michael,

I have selected BASIC_INFO_ALL/GROUP tabs under Read & Write Nodes, but still not working.

Basically, whenever a Group is changed, I would like to make sure my custom node determination is triggered. I have the another custom field control profile under the BASIC_INFO_ALL, which is getting triggered all the time, but not this custom node profile.

Would those 2 checkboxes(Check Method/Delta Method Implemented) be a concern here? What are they for?

Regards,

Udit

[michaelf_]

Hi udit31 ,

if you want to base your field control profile on the change other nodes, you have to mark these in the determination configuration configuration as Change/Create. I believe there are some examples available for the Person Injured Information/Regulations (show specific fields for U.S. OSHA).

Regarding the Check / Check Delta: These methods can be used to change the node instances, the determination will be executed for. As an example, Check could be used to only run the determination for Incidents (and not for Near Miss of Safety Observations), Check Delta could be used to only run the determination if a certain field was changed.

When using the properties/field control, these two methods are not used/relevant, as long as they don't remove any keys from the CT_KEY parameter. (if you're using the standard EHS class for field control, the CT_KEY is not changed, and therefore the determination is run for all instances).

With kind regards,

Michael

[Utrivedi]

Hi Michael,

No change at all. Let me try to share my configuration, if you can spot anything I might be missing.

[Utrivedi]

...Continue

And nothing in the determination dependency. I have seen the similar pattern in the standard Set Properties determination.

Injured Person/Regulation did have the similar configuration.

Regards,

Udit