Wiki Detay | wiki workcube

There are different customization options on Workcube. Page designer, included in the Definition and Setting customizations, is one of them. With the Page Designer, all elements on the screen (form elements, input, selectbox, etc.) can be changed, removed, or arranged as mandatory fields. In addition, extra new fields can be added to the page in the page designer. Extended Fields is a tool that allows adding extra new fields to forms on the page via Page Designer.

Designing Extended Fields

Path:Control Panel > System > Page Designer

On the left side of the Page designer screen, there are Extended Fields to be designed and the elements below. These are;

Text Input: Field where text or number data can be entered.
Hidden Input: A hidden value that carries the form data that the user does not see in the interface, on the code side. For example; id values
Selectbox: A drop-down list where options are selected from a specific list. Selectbox allows the data to be selected to be listed.
Textarea: Text area where multi-line text can be entered.
Radio Button: Button-shaped areas that offer options to the user and only one option can be selected.
Checkbox: In case the user is given an option and an option is checked or unchecked.

First of all, fields are moved to the desired columns using the drag and drop method among the above elements.

After adding the desired field to the column, click on the settings (gear) icon on the right. It is determined how and in which direction the added element will work. Selection criteria in the field;

Label: Naming the added field. Here it is mandatory to choose a word from the dictionary. If the desired word is not in the dictionary, it can be selected after it is added to the dictionary.
Required: Makes it a required field.
Data Type: Opened if text input or hidden input is selected.
Numeric: Numeric value is entered. The maximum and minimum value to be entered can be given in this field.
Alphanumeric: Both numerical and letter values can be entered.
Date: Date value can be entered.
E-mail: e-mail value can be entered.
Phone: Phone number can be entered. is provided.
DB Field: It is determined which fields will be retrieved from the database as a result of the search process.
Option Settings: Opens if a checkbox or radio button is selected. Many options can be added. A separate number and text should be added for each option.

After all adjustments are completed, they are saved with the "Save" button. Unsaved edits will not be valid.

If the edits are not desired, they can be canceled with "Cancel". Accordingly, changes will not be added or updated.

If "Remove" is selected, the adjustments will not be saved and the field you added via drag and drop method will be removed directly from the column. will be removed.

Attention: After the save settings are saved, they will be saved in the "Page Designer" side. It should not be forgotten to click the “Save” button. Otherwise, the changes made with "Extended Fields" will not be valid.

Recommendation: For detailed information about the Page designer, see the "Screen Arrangements" document.

Notes to Developers

The following situations may prevent the Extended Fields feature from working. When it is determined that the Extended Fields feature is not working, the following situations should be checked and intervened.

1. Wo - Controller differences

Page designer page settings are kept according to controller and event values. Extended Fields properties are also related to the table that keeps the page designer records.

Since the actions of some forms are different from the existing fuseaction, the controller paths are also different. In such cases, even if you configure the page designer settings of the page, Extended Fields will not work because the post action will be performed in a different fuseaction.

Ex:

Purchase request fuseaction: purchase.list_purchasedemand (controller exists), form action: purchase.emptypopup_add_internaldemand (controller). none)

In this case, when you add an extended field via the page designer on the form screen and save it, the field added to the form appears, but since the action fuseaction is different, it cannot capture and connect the query side with fuseaction or controller values.

Such pages must work with the controller in a single fuseaction or be converted to the datagate infrastructure so that the extended fields feature can be used.

Similarly, these pages are for the above reason. It cannot benefit from extensions features either.

2. Manual redirection on the action page

After the post operations, url redirects were made manually in the action file with cflocation or script, and the parts of the form_converter or basket_converter files after the action code was run were equalized. For this reason, cf_extendedfields customtag does not work either.

When this situation occurs, manual redirects in action files should be removed and next_event should be defined in the controller file and an identity value should be assigned to the attributes.action_id parameter.

Similarly, these pages cannot benefit from extensions features for the above reason.

3. action_id assignment problem

Since the identityid value created after adding the action files of the forms is not assigned to the attributes.action_id parameter, data cannot be written to the table by establishing a record-based relationship.

When this situation occurs, it is necessary to assign the identity value to the attributes.action_id parameter on the bottom line after the addition process is completed in the insertion files. In update operations, the identity parameter should be defined in the struct of the relevant event in the controller and the id value of the record should be given, or the attributes.action_id value should be assigned as in the addition in the update action file.

Feedback

Did you find this content helpful?

Please Write Your Feedback!

Name*

Last Name*

Email *

About Workcube Objects

Record was not found