View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

ERP/3.0/Developers Guide/Database Model/org.openbravo.client.application/OBUIAPP Process

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to ERP/3.0/Developers Guide/Database Model/org.openbravo.client.application


Contents

OBUIAPP_Process

This table contains the following columns:

Name Nullable Data Type Description


Obuiapp_Process_ID No VARCHAR (32) Process Defintion is a re implementation of Process with 3.0 infrastructure.
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
AD_Org_ID No VARCHAR (32) An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
Isactive No CHAR (1) There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reporting. There are two reasons for de-activating and not deleting records:

(1) The system requires the record for auditing purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are existing invoices for it. By de-activating the Business Partner you prevent it from being used in future transactions.

Created No TIMESTAMP (7) The Created field indicates the date that this record was created.
Createdby No VARCHAR (32) The Created By field indicates the user who created this record.
Updated No TIMESTAMP (7) The Updated field indicates the date that this record was updated.
Updatedby No VARCHAR (32) The Updated By field indicates the user who updated this record.
Value No VARCHAR (40) A search key allows for a fast method of finding a particular record. If you leave the search key empty, the system automatically creates a numeric number originating from a document sequence defined in the "Document Sequence" window. The sequence naming convention follows a rule "DocumentNo_TableName", where TableName is the actual name of the database table (e.g. C_Order).

Usually, company's internal identifiers for various records (products, customers, etc) are stored here.

Name No VARCHAR (60) A more descriptive identifier (that does need to be unique) of a record/document that is used as a default search option along with the search key (that is unique and mostly shorter). It is up to 60 characters in length.
Description Yes VARCHAR (255) A description is limited to 255 characters.
Help Yes VARCHAR (2000) The Help field contains a hint, comment or help about the use of this item.
Accesslevel No VARCHAR (60) Indicates what type of data (in terms of AD_CLIENT and AD_ORG data columns) can be entered or viewed. We can classify data in 4 major categories:

- System (AD_CLIENT_ID=0, AD_ORG_ID=0) - system data (such as metadata for window, tab and field definition) - Organization (AD_CLIENT<>0, AD_ORG_ID<>0) - data particular to an organization (such as sales orders) - Client/Organization (AD_CLIENT<>0, AD_ORG_ID=anything) - data particular to an organization or shared among all organizations within one client - Client (AD_CLIENT<>0, AD_ORG_ID=0) - data that is specific to a client but can be used by all organizations within that client

or All (AD_CLIENT=anything, AD_ORG_ID=anything)

Classname No VARCHAR (200) The classname is used when generating a representation of the table in java (the entity or business object). The classname is the simplename of the class (so without the package name). Often the AD_Table.name can be used here. The combination of classname and package needs to be unique.
Isbackground No CHAR (1) This identifies a background process that will be run without any user interaction and needs to be scheduled properly before it will be run using the "Process Scheduling" window.
AD_Module_ID No VARCHAR (32) Indicates the module the element forms part of.
Uipattern No VARCHAR (60) Defines the UI Pattern that the object implements.
IsMultiRecord No CHAR (1) Multi Record allows to execute the process in multiple records at the same time. When this flag is set, multiple records can be selected in grid mode and the process can be executed in all of them at the same time.
Is_Explicit_Access No CHAR (1) When processes are executed from a button in a window, by default, they inherit permissions granted to the window. So if the window is accessible it can be executed without the need of explicitly granting access for that role to the process.

This behavior can be overwritten by the "Secured Process" preference.

Processes with "Requires Explicit Access Permission" flag set to true, do not inherit permissions from the window but they always require the role to be explicitly granted to this process.

Clientsidevalidation Yes VARCHAR (200) JavaScript function to be executed before invoking the backend Handler.

This function (manually coded), can:

- Perform validations on the parameters, being possible to prevent execution in case these validations are not satisfied.
- Request for additional info to complete the parameter values.
Isgridlegacy No CHAR (1) This flags is used to specify if this process should be compatible with the legacy parameter windows.

The legacy parameter windows could only contain one grid, so the _selection and _allRows properties of the grid were directly accessible in the handler from the params object. I.e:

JSONArray gridRows = jsonparams.getJSONArray(ApplicationConstants.ALL_ROWS_PARAM);

New process definitions should access these value like this: JSONObject myGridItem = jsonparams.getJSONObject("myGridItemName"); JSONArray myGridSelectedRows = myGridItem.getJSONArray("_selection");

The 'Compatibility with Legacy Grids' flag should only be checked if its handler retrieves the grid values in the old way.


ON_Load_Function Yes VARCHAR (200) In this field a javascript function can be defined. This function will be executed when the parameter window is loaded, just after the default values are set.
IsCanAddRecordsToSelector No CHAR (1) By selecting this flag, the process will be available in the 'Defined Selector' window.

This process has to be capable of adding records to a selector.

ON_Refresh_Function Yes VARCHAR (200) In this field a javascript function can be defined. This function will be executed when the parameter window refresh action be invoked. For example, if the process has a child-process, once the child-process finishes, it will invoke a refresh of the parent process.

Since each process has its particularities, a custom refresh function should be defined in case the process be susceptible of being refreshed/reloaded.

Columns

Obuiapp_Process_ID



top


Client


Foreign key column to AD_Client table, (column: AD_Client_ID)

top


Organization


Foreign key column to AD_Org table, (column: AD_Org_ID)

top


Active



top


Creation Date



top


Created By


Foreign key column to AD_User table, (column: AD_User_ID)

top


Updated



top


Updated By


Foreign key column to AD_User table, (column: AD_User_ID)

top


Search Key



top


Name


top


Description



top


Help/Comment



top


Data Access Level



List values: AD_Table Access Levels

The allowed values for this list are:

top


Java Class Name



top


Background



top


Module


Foreign key column to AD_Module table, (column: AD_Module_ID) It has a validation "Ad_Module_ID IsInDevelopment", with the following code

IsInDevelopment = 'Y' and type != 'T'

top


UI Pattern


List values: Process Definition UIPattern

The allowed values for this list are:

top


IsMultiRecord



top


Requires Explicit Access Permission



top


ClientSideValidation



top


Isgridlegacy



top


ON_Load_Function



top


Can Add Records to a Selector



top


ON_Refresh_Function



top


Other Info

Check Constraints

These are the check constraints for this table:

top

Back button.png   Back to org.openbravo.client.application

Retrieved from "http://wiki.openbravo.com/wiki/ERP/3.0/Developers_Guide/Database_Model/org.openbravo.client.application/OBUIAPP_Process"

This page has been accessed 654 times. This page was last modified on 2 March 2016, at 13:05. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.