Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: What is IDF and how could it make my life easier?

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

  • Arrange application information into multiple groupings and sequences that make sense for the job.
  • Hide information that does not apply to a particular job or task.
  • Filter records to show only the information that applies to the job or task that the user is performing.
  • Customize the information for an individual user, for a group of users, or for all users.
Previous Article Infor LN & Baan Tip: Deleting Records
Next Article Infor LX & BPCS Manufacturing Tip: Backward Scheduling
Print
29017 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Read more

Categories