This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
cecille:sa [2016/08/26 01:40] ca |
cecille:sa [2016/08/26 15:23] (current) ca |
||
---|---|---|---|
Line 7: | Line 7: | ||
- | |||
- | ==== Business ID==== | ||
- | |||
- | * In order for us to enter any data for a Company we first need to set up a new business entity. | ||
- | * The Company name should be unique, that means you cannot create two companies with exactly the same name. | ||
- | * Take note <wrap em>red Highlights</wrap> are Mandatory Field you need to fill-in. | ||
- | |||
- | business_id.pptx | ||
- | | ||
- | |||
- | ====PORTAL==== | ||
- | |||
- | * This is an integrated admin portal for you to manage the sites, their settings, access rights from anywhere and anytime. | ||
- | * You also Use this to congfigure or maintain your company database of items, costumers, suppliers, brands, price,tables, accounts,receipts,payments, etc… | ||
- | * Portal is a term, generally synonymous with gateway. | ||
- | * Typical services offered by portal sites include a directory of Web sites, a facility to search for other sites, e-mail, stock quotes, and sometimes a community forum. | ||
- | |||
- | |||
- | ====User's & Security==== | ||
- | |||
- | * a very fine-grained level of detail in assigning permissions. | ||
- | * User-level security allows the database administrator to group users with similar needs into common pools. Permission can then be granted to work group instead of to individual users, easing the administration of permissions. | ||
- | |||
- | **The importance of User's, Roles and Permissions** | ||
- | |||
- | - Users are the people | ||
- | - roles are their functions,and | ||
- | - permissions define what authorizations those functions have. | ||
- | |||
- | ===ROLES=== | ||
- | |||
- | * This is a principle by which developers create a systems that limit access or restrict operations according to a user's constructed role within a system. This is also often called role-basedprinciple to ensure that authorized users do not gain access to privileged information. | ||
- | |||
- | ===TEAM=== | ||
- | |||
- | * After you have defined the Team, you can link the Team member to the Team and Role. By doing so, you can access to any of the transaction entry by Team. | ||
- | |||
- | ===LIMIT== | ||
- | |||
- | * The function on user Limit is activated for a particular transaction type only if you have set any limit for at least one user for one transaction type. | ||
- | |||
- | ===Visibility=== | ||
- | |||
- | * Once you set up any value for a particular context, all users not satisfying the condition will be barred from viewing any record in all lists in the system. | ||
- | |||
- | **<wrap em>The best practices for securing your system users, roles, and permissions are based on the following ideas:</wrap>** | ||
- | |||
- | Rethink your roles | ||
- | Know the defaults | ||
- | Evaluate your elevated permissions | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ====Data Tools==== | ||
- | |||
- | * wherein the process of analyzing data from different perspectives and summarizing it into useful information take place. | ||
- | * Uploading of Master File take place. | ||
- | * Data Tools“ is a vast domain, yet there are a fairly small number of foundational requirements when developing with or managing data-centric systems. Data management, whether by a developer working on an application, or an administrator maintaining or monitoring a production system, should provide a consistent, highly usable environment that works well with associated technologies. | ||
- | |||
- | * Such an environment starts with key frameworks designed both for use and extensibility. Examples include location and management of data source drivers, and configurations for access to particular data source instances. Once a connection is successfully made, the next task often is to explore the data source, making changes as required. Some of these operations might be carried out by GUI actions, others directly through commands. For example, users - both developers and administrators - typically will create, edit, and test SQL for these commands. Assistance in editing SQL through code completion, formatting, and dialect specialization, greatly enhances productivity. Further, the ability to execute or debug commands, both SQL and stored procedures, rounds out the rapid development process. Finally, bridging chasms, whether between relational, object, or other structures, presents challenges that data management tooling should address. | ||
- | * Graphical User Interface (GUI), is a type of user interface that allows users to interact with electronic devices through graphical icons and visual indicators such as secondary notation, instead of text-based user interfaces, typed command labels or text navigation. GUIs were introduced in reaction to the perceived steep learning curve of command-line interfaces (CLIs),[1][2][3] which require commands to be typed on a computer keyboard.The actions in a GUI are usually performed through direct manipulation of the graphical elements | ||
- | * **Structured Query Language (SQL)** consists of a data definition language, data manipulation language, and Data Control Language. The scope of SQL includes data insert, query, update and delete, schema creation and modification, and data access control. Although SQL is often described as, and to a great extent is, a declarative language (4GL), it also includes procedural elements. | ||
- | * **CSV Files** is a **Comma Separated Values File**, which allows data to be saved in a table structured format. CSVs look like a garden-variety spreadsheet but with a .csv extension (Traditionally they take the form of a text file containing information separated by commas, hence the name). CSV files can be used with any spreadsheet program, such as Microsoft Excel, Open Office Calc, or Google Spreadsheets. They differ from other spreadsheet file types in that you can only have a single sheet in a file, they can not save cell, column, or row styling, and can not save formulas. | ||
- | * //What can I use CSVs for?In e-commerce, CSVs are used primarily for importing and exporting product, customer, and order information to and from your store.// | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ====Logs and Lists==== | ||
- | * The Detailed Monitoring and Recording of transactions made by different users in the system. | ||
- | **Types:** | ||
- | Error/Transactions Logs | ||
- | History Logs | ||
- | Users/Role Lists | ||
- | Codes List | ||
- | Transaction Code Lists | ||