{{ model.title }}
This page is currently being edited by {{ model.editingBy }}.6.106
- added more information related to APPCOMBO inputs and gave examples of how to build these within the scripts.
Base URL: https://idcloud.yoursp.com/C2SDocumentSearch/DocumentSearch.aspx?
When setting up an input page for Milner ImageDirector, make note of the following.
- Which fields will be pulled from this page.
- Which fields must the user input for a particular application.
- Which types of input will be needed.
- Which fields will have hardcoded input while showing.
- Sort order
- APPCOMBO inputs
For calling the input builder, we'll need to manually make a list of MilnerFields with the QueryName that milner uses as well as the input from the smartfusion page we want to pass into it. Once this list is built, we can call the initializePage method for the MilnerUI and pass in the list of MilnerFields we just created.
When adding a new application and determining the fields we want to pass into our queries, We'll want to make a new script for adding these values to the QueryCodes table. The fields input will have a sortOrder number > 0 which will determine their placement on the dynamic screen. The fields will be further explained below.
Another part of the script will determine what the input type will be. For now,we are only using textboxes or date dropdowns. AppCombo is used for application selecting if a page has need of more than 1 application.
The QueryCode table has a field for any hardcoded input that will be displayed in the input.
Sort order is the order in which fields will be displayed on the input page. On the code side, any pulled data will not be used on the particular dynamic page, but a sort order can be added in case there ever is a time for there to display that particular input field.
When using APPCOMBO input types the QueryType will be the name you use to map to the correct applications for the drop down. The querytype for enteredit UB for example is UBCUSTOMER. any APPCOMBO inputs for this one will map to a Code which will be the query type of the correct inputs for the application. For example, the UBCUSTOMER will map to the UTILITY and the BILLRUN applications which have their own inputs. The sortorder for these are the order in which they appear in the dropdown.
example of dropdown fields
example of the inputs associated with the applications.
Data Field | dataType | Length | Definition | ||
---|---|---|---|---|---|
1 | QueryCodeID | int(ID) | ID | ||
2 | QueryType | varchar | 50 | Which Application this input is for | |
3 | Code | varchar | 50 | The MilnerQuery name of the field | |
4 | Description | varchar | 255 | what our label will call this field | |
5 | SortOrder | int | which input this corresponds to | ||
6 | HardCodedInput | varchar | 50 | for hardcoded input (leave blank unless being used" | |
7 | InputType | varchar | 10 | The type of input (text, date) | |
8 | AllowSearch | bit | Use this field for searches. |