CUSTOMER Application Development Workshop

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the correct naming convention for the version created for the CUSTOMER application?

CUSTOMER_APPLICATION

CUSTOMER_XX

CUSTOMER.VERSION

CUSTOMER,XXX (correct)

Which of the following fields should be displayed in the CUSTOMER version?

ACCOUNT.TYPE

PHONE.NUMBER

NATIONALITY (correct)

What change is made in Workshop 3 regarding the SECTOR field?

It is set to read-only mode.

It defaults to a value of 500.

It is defaulted to a value of 1000 and made NOINPUT. (correct)

It is made a mandatory field.

What condition triggers a default value of 'IN' for the NATIONALITY field?

If the previous value was 'US'. Signup and view all the answers

Which field must be made mandatory according to the directives in Workshop 3?

CUSTOMER.STATUS Signup and view all the answers

What value should be defaulted in the CURRENCY field according to the requirements for the version?

USD Signup and view all the answers

Which field is required to be mandatory even though it is not part of the ACCOUNT application?

SHORT.TITLE Signup and view all the answers

How should the CATEGORY field be treated once a record is authorised?

It should be set as a NOCHANGE field. Signup and view all the answers

What will happen if a mandatory NOINPUT field does not have a default value?

The record cannot be committed. Signup and view all the answers

What property is used to prevent changes to the CATEGORY field after record authorization?

NOCHANGE property Signup and view all the answers

What is the purpose of the NOINPUT property for certain fields?

It prevents users from inputting or amending field contents. Signup and view all the answers

What value should overwrite an existing value in ACCOUNT.TITLE.1 that starts with 'TEM'?

'Training' Signup and view all the answers

When using the VERSION application, what does the AUTOM.FIELD.NO specification do?

It indicates the name of the field for default value assignment. Signup and view all the answers

What is the purpose of the MANDATORY.FIELD in a version?

The MANDATORY.FIELD specifies the field name that must be filled in by the user, making it mandatory to commit the record. Signup and view all the answers

Can a non-mandatory field be made mandatory in a version?

Yes, a non-mandatory field can be made mandatory in a version. Signup and view all the answers

What happens if a user does not enter a value in a mandatory field?

The user will not be able to commit the record if they leave a mandatory field empty. Signup and view all the answers

How does setting the CURRENCY field default to USD affect record creation?

It ensures that every new account record will automatically have 'USD' set in the CURRENCY field. Signup and view all the answers

Describe the role of the SHORT.TITLE field in the context of mandatory fields.

The SHORT.TITLE field is made mandatory, requiring the user to input a value before committing the record. Signup and view all the answers

What is the result of marking a field as NOCHANGE after authorization?

Once a field is marked as NOCHANGE, its value cannot be altered after authorization. Signup and view all the answers

How does the replacement of values using AUT.OLD.CONTENT and AUT.NEW.CONTENT work?

It replaces the value specified in AUT.OLD.CONTENT with the value in AUT.NEW.CONTENT. Signup and view all the answers

What effect does the defaulting of the CURRENCY field have on existing records?

The CURRENCY field will default to USD regardless of whether it is a new or existing record. Signup and view all the answers

What is the significance of including MNEMONIC and CUSTOMER NUMBER on the same line in the ACCOUNT version?

It enhances user experience by allowing related information to be viewed together for easier data entry. Signup and view all the answers

Why must certain fields be included in the version for customization?

Including certain fields allows users to edit and interact with default values directly, ensuring flexibility and accuracy in data management. Signup and view all the answers

What role does the FIELDS.PER.LINE setting play in the version display?

The FIELDS.PER.LINE setting, when set to MULTI, allows multiple fields to be displayed on the same line, streamlining the layout. Signup and view all the answers

What does appending '-1' to a multi-value field name denote?

It indicates that the field is expected to hold multiple values, allowing the system to manage the data correctly. Signup and view all the answers

How does the TEXT.CHAR.MAX parameter affect field labels?

The TEXT.CHAR.MAX parameter defines the maximum length for field labels, ensuring they fit well within the user interface. Signup and view all the answers

What is a key consideration when creating user-defined labels in the version?

User-defined labels must be clear and descriptive to convey the purpose of the fields effectively. Signup and view all the answers

Why is it necessary to define which fields must be displayed in the CUSTOMER application version?

It ensures that critical information is always included and visible for users, improving data integrity and usability. Signup and view all the answers

What is the effect of customizing output in the T24 system?

Customizing output helps tailor the application to specific user needs and workflows, enhancing overall efficiency. Signup and view all the answers

Study Notes

Workshop 1

Create a version for the CUSTOMER application
The name of the version should be CUSTOMER,XXX (where XXX is your initial)
The following fields should be displayed:
- MNEMONIC
- SHORT.NAME
- NAME.1
- STREET
- SECTOR
- Account Officer
- INDUSTRY
- TARGET
- NATIONALITY
- CUSTOMER.STATUS
- RESIDENCE
- LANGUAGE

Workshop 2

Amend the previously created version to display two fields in a row rather than one

Workshop 3

Amend the previously created version as follows:
- Default value for SECTOR should be 1000
- Make SECTOR a NOINPUT field
- Default value for NATIONALITY should be IN if the previous available value is US
- Make CUSTOMER.STATUS a mandatory field
- Ensure the value of ACCOUNT OFFICER cannot be changed once the customer record is authorized

Version Application

T24 uses a system called "Versions" to modify screen displays and behavior.
Versions provide an easy way to customise applications by modifying standard screens.
Versions are independent of the original application and can be used for both new and existing records.

Defaulting Values in Versions

Values can be automatically entered into fields when a record is opened using the version.
To achieve this, define AUTOM.FIELD.NO (field name) and AUT.NEW.CONTENT (desired value).
This defaults the specified value into the field, making it a "pre-filled" input.

Noinput Field Property

NOINPUT field property prevents users from editing or entering values into specified fields.
Fields with this property appear greyed out.
Multiple fields can be designated as NOINPUT using this property.
If a mandatory field is made NOINPUT, it is essential to default a value for that field. This ensures that the version can commit records successfully.

Nochange Field Property

NOCHANGE fields prevent modifications after record authorisation.
Fields marked NOCHANGE appear greyed out once authorised, ensuring their values remain consistent.
This property is used to restrict changes to specific fields after a record is approved.

Defaulting Values Using Find and Replace

The fields AUT.OLD.CONTENT and AUT.NEW.CONTENT can be used to replace existing values.
The AUT.OLD.CONTENT specifies the value to find, and AUT.NEW.CONTENT specifies the new replacement value.
Example: If you want to replace "TEM" at the start of a field with "Training," set AUT.OLD.CONTENT to TEM0X and AUT.NEW.CONTENT to "Training.
- "TEM" represents the starting string.
- "0X" acts as a wildcard, matching any number of characters following "TEM".
- Replacing the existing value ensures uniformity even when the field is not mandatory.

Mandatory Field Property in Versions

Non-mandatory fields in the application can be made mandatory within a specific version.
To enforce mandatory fields, specify the field name in the MANDATORY.FIELD section of the version.
Users must provide values for mandatory fields, otherwise committing the record will be prohibited.

Viewing and Customizing Versions

Versions are displayed as customized screens tailored to the specific requirements defined in the version.
Though customized, the underlying application functions remain the same within the T24 environment.

Workshop Example

Creating a version for the CUSTOMER application.
The version name will be CUSTOMER, followed by your initials.
This version will include the following mandatory fields: MNEMONIC, SHORT.NAME, NAME.1, STREET, SECTOR, ACCOUNT.OFFICER, INDUSTRY, TARGET, NATIONALITY, CUSTOMER.STATUS, RESIDENCE, LANGUAGE.

Displaying Multiple Fields on One Line

Use FIELDS.PER.LINE property set to MULTI to arrange multiple fields on the same line.
For example, displaying MNEMONIC and CUSTOMER NUMBER side-by-side.
Set COLUMN to 1 for fields displayed on the same line.

Text Label Adjustment

The TEXT.CHAR.MAX property controls the maximum character length for labels.
Adjusting this property allows for labels to display with appropriate length for clarity.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Description

This quiz covers the workshops focused on developing a CUSTOMER application. Participants will learn to create and amend data fields, set default values, and enforce field constraints. The workshops aim to enhance the functionality and user experience of the application.