all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||||||||
|
|||||||||
|
|
|
Notes:
|
|
-On the content server… set up the model so that we could separate content and data or that we can combine it together on different drives. Our current model is together on the same machine but on different drives. That works… but it may be better to separate things for growth and task separation. With images… it may not be a big deal… however with PDF, music, video, power point, it could be a big deal to keep things separate. -What if we allowed users to upload whatever they wanted for any of the main players. We then show them what is attached and how to get to it. -To secure their info, you could always store it in a database per company or per corporation. -It might be nice to have a recorded file name and a stored file name. Basically an alias. You call it whatever. We’ll store that. We’ll call it what we want and then we’ll show you what you called it. -On custom code – we could actually are things in a database and then call these defaults and settings at runtime. Or we could store in the database, push on publish, and then run on what was published. This may be part of the inline custom code option. -The code stored in the database could even be as simple as what page to use to show, edit, add or view. It could print to a flow on a process. Say for example we set up flow and standard check points. We then allow a user to use any of the standard check points and flow but the rules (how the application plays) could be recorded and defined by a user. This could allow for custom processes that get defined at the application level. To further define this idea, say we had a standard procedure like this: To create an invoice – normal – quick sale (Say this was a pre-defined process) 1. Start cart, choose location and cart type 2. Go to view cart page 3. Allow for items to be added - Normal search and add - My cart favorites - Smart groups - Recipe/builds - Advanced add to cart - Preset special line items - Other 4. Click the checkout button 5. Prompt for payment info - Normal payment options - Special merchant processing 6. Create invoice - Preview first - Direct create 7. Send user to a predefined printable invoice page based on corp-wide settings. What if you could change the process at the application level….?? For example: (inline modified process) 1. Click a button. This button starts the cart, sets the type and location and sends the user to a point and click interface. 2. The user makes the selection and the page automatically advances to the merchant processing page for credit card payments. 3. The credit card is swiped and once approved it automatically shows a custom invoice designed by the company. What if you could use this custom process (above) without leaving adilas. Think of it as “inline custom code.” User defined processes… |