Xpodium Application Development Guide

While developing the Xpodium application, the following points should be taken into consideration.

❖ After the information for the application application is submitted, the preliminary code for development will be sent to you after the review.

❖ Applications; It is developed in three different types: Free, Locked and Readonly.
* In free applications, all users can view and make changes to the application in Studio.
* Locked applications are the type where users cannot view or change the application in Studio.
* Readonly applications are applications that can be viewed in Studio but cannot be modified.

❖ All forms in the application must be developed through Xpoda Studio. Any tables, reports or forms that do not exist in Xpoda Studio will not be available in the application.

❖ Table naming should be such that all letters are capitalized and there is a '_' (underscore) between words. (Ex: XPT80_PERMISSION_REQUESTS)

❖ All tables must be initialized with the precode provided by Xpoda. The table name must not contain Turkish characters. (Ex: XPT70, XPT80)

❖ If the Xpodium product contains more than one module, the process should be reported to Xpoda and the Xpodium code should be incremented regularly as in the example. (Ex: Xpodium code: XPT85 1. Module: XPT85_PERMISSIONS 2.Module= XPT8501_REQUESTS 3rd Module: XPT8502_PERSONNEL)

❖ When field naming, the first letters should be capitalized and there should be no spaces between the words. (Ex: AuthorizedUser)

❖ Field and table naming should not include each other. (Ex: City, District, not Province, District)

❖ The form field and label must have the same name.

❖ Forms and fields should not be copied even within the project.

❖ The Xpodium application icon will be provided by us in accordance with Xpoda design standards.

❖ The names of all functions and procedures used in the application must be started with the precode. (Ex: fn_XPT80_Bracket)

❖ The scripts of all functions and procedures used in the application should be shared with Xpoda as a single file in the order of creation, with the Go command in between. (Ex: Attachment 1)

❖ In order for the application to be published on Xpodium, the following information must be shared with Xpoda in full. (Ex: Attachment 2)

Attachment 1

Attachment 2