This topic briefly lists the new features in this release of the product.
This version of SyteLine is compatible with these product versions:
This version of SyteLine integrates with these products:
This version addresses performance problems that some customers encountered with data rendering, particularly where image data and the tile feature were combined.
The changes described in this section were made to comply with US government FedRAMP security requirements.
Now users can be considered "inactive" if they have not logged into the system for a specified number of days. The system keeps track of the last date when any activity by each user in SyteLine was recorded.
This information is stored for each user in the new Last Active Date field on the Users form. System administrators can set a value, in days, for the new User inactivity threshold process default. If a value is set, then when a user logs in, the user's Last Active Date is compared to the current date. If the difference is more than the number of days specified for the User inactivity threshold, the login is refused, and the account is disabled.
You can now optionally use token-based authentication as an additional layer of login security. If you set up this layer, users are prompted for a user ID, a password, and a token-obtained passcode during login. To set this up, you select the new Token Authentication option and specify an authentication Service URL in the Configuration Manager, and click the new Validate Service button. Then, in the new Passcode Mapping field on the Users form, specify the mapping of the SyteLine user name to the token authentication system user name. For more information, see the help topic Token Authentication in Mongoose Applications.
Note: If you plan to use this feature, you must purchase and configure an RSA SecurID.
System administrators can now use the process default, Browser inactivity lock minutes, to lock the browser of any user who leaves the current session idle for longer than a specified number of minutes. For more information, see the help topic Setting a Lockout for Session Inactivity.
The encryption of passwords in SyteLine is now compliant with Federal Information Processing Standard (FIPS) publication 140-2. This encryption applies to the Usernames and OutriggerProfile tables of the application database, as well as the SQL user ID and password, data source name, and database name stored in the MongooseConfigs.xml configuration file. As much as possible, backward compatibility with older versions of the IDO Request service and their existing methods of encryption has been maintained. However, after data is updated in databases or XML files with the new encryption, then those databases and files must be accessed with a version of the application that supports the new encryption algorithms. If attempts are made to access this data with older versions, errors result. For more information, see the topic Troubleshooting configuration-related problems in the Configuration Manager online help.
System administrators can now set a minimum number of days between password changes for users. This feature is intended to prevent users from quickly cycling through the Password History Count in order to keep the same password indefinitely.
To set up this feature, specify a number of days in the new Password Minimum Days field on the Password Parameters form. Whenever users update their passwords, the new Password Set Date value is updated on the Users form, and the specified number of days must pass before the user can reset the password again. System administrators can override this setting if necessary. For more information, see the help topic Setting Password Parameters.
New security options are available in the Configuration Manager to restrict script code from accessing protected machine resources. This is especially significant in a Software-as-a-Service (SaaS or Cloud) environment. See the information about "Smart Client Scripts Run In Partial Trust" and "Web Client Scripts Run in Partial Trust" in the Configuration Manager online help.
A new Application Event System event, IdoOnPersistFailed, is generated whenever an exception or failure occurs during a create, update, or delete operation. This event captures key contextual information about the update collection IDO request and the reason for the exception or failure. You can create event handlers and actions to record this information in a log or to notify an administrator when the event occurs. For more information, see the description of the new event in the Guide to the Application Event System.
A new Application Event System event, SessionOnLoginFailed, is generated whenever a failure occurs during a client login attempt from any tier. This event captures key contextual information about the user name, application ID, location of the client, and the reason for the failure. You can create event handlers and actions to record this information in a log or to notify an administrator. For more information, see the description of the new event in the Guide to the Application Event System.
System administrators and form or application developers can now specify a custom "About" message that is displayed in the Sign In dialog box when a user selects a configuration. The same message is displayed in the About SyteLine window. To set up the message, use the Additional About Message field in the Configuration Manager.
If the new Use Alternate Address Report Formatting field on the General Parameters form is selected, reports that are sent to customers and vendors use an alternate format for addresses. The alternate address format is set up as:
Company Name
Contact Name
Address 1-4
Zip Code City
Country
Also, if the Use Alternate Address Report Formatting field is selected, reports that are sent to customers and vendors print your company's return address as a single line, with fields separated by commas, in a smaller, underlined font, above the mailing address. Because of limited space when the return address is converted to a single line, the full return address might not be viewable in an envelope window. To avoid this problem, we recommend that you only use the Address 1 line when you set up the return address. The address from the General Parameters form is used as the return address on these reports:
On the Print Price Adjustment, Order Invoicing Credit Debit Memo, and RMA Credit Memo reports, the Tax Summary area of the report now includes an Extended Tax column. This is a calculated value based on the tax rate multiplied by the tax basis.
On the Consolidated Invoicing report, the item tax code and tax summary are added.
For customers or vendors in European Union countries, you can enter the customer or vendor VAT number in the [Tax ID Label 1] field on the Customers, Customer Ship-Tos, or Vendors form.
The EU mandates that all VAT numbers must be verified yearly. You can click the new VAT Validation button next to the [Tax ID Label 1] field to pass the specified VAT number to the VAT Information Exchange System, which verifies that the number is valid for each EU member. A success or failure message is returned, and the date when the verification expires is stored in the customer table. When the validation is successful and you save the record, all customer ship-to records with the same VAT number, EU code and tax code are also updated with the new date.
The icon next to the button indicates whether the VAT number has been verified within the last year (green check mark) or needs to be verified (red X).
This button is displayed on the Vendors, Customers and Customer Ship-Tos form when the EU code is populated.
The VAT number must be verified in either of these scenarios:
These forms now include a test to determine if the customer’s VAT number is valid at the time of an order due date or shipment date:
If the number is not valid at the ship date/due date, a warning message is displayed. However, you are still allowed to ship the order.
Intrastat is the system used to collect information and produce statistics on the trade of goods between countries in the European Union (EU). The requirements are the same for all EU member states, but the data format is not the same. Previously, SyteLine used the UK intrastat format, which was not appropriate for all EU countries. To support Intrastat use in Germany, we added a State SSD Tax ID field on the Prov/States form. The appropriate values for this field are to be provided by the German Federal Statistical Office. In the EU SSDs form, use the Tax District field to specify the State SSD Tax ID value that is to be used when you generate the Intrastat SSD data file. SyteLine now allows these different SSD File Option formats for the declaration on the EU Supplementary Statistical Declaration Report form:
To support the ASCII and XML formats, these new fields were added to the Tax Parameters form: SSD File Directory, SSD Dispatch Interchange ID, and SSD Arrival Interchange ID. For more information, see the help topic Setting Up Information for the EU SSD Report.
Infor PCM Document Automation is a separately purchased product used to create configurable documents - for example, proposals that include MSDS (material safety data sheets), drawings, cover letter, and specifications. You can combine various pieces of documentation to build a single document. You can also build documents such as manufacturing instruction sheets, additional shipping information, or sales order addendums that further describe the options in a configured product.
Now you can launch Infor PCM Document Automation from the new Actions > Generate Document option or Generate Document button on these SyteLine forms:
This option and button are displayed only if the new Application ID and Name Space fields on the Inventory Parameters form are populated with Infor PCM Document Automation values. The new Default Rule Set field on that form is also used with Document Automation.
When you select the option or click the button, a new Configuration Rule Sets form is displayed, if you did not specify a Default Rule Set in Inventory Parameters. Use the Configuration Rule Sets form to select a rule set to generate the document. This form does not belong to a default authorization group, so the system administrator must assign individual users to the form or create a group.
For information about setting up rule sets in Infor PCM Document Automation, see the Infor Product Configuration Management Document Automation Installation and Setup Guide.
Documents generated by Infor PCM Configurator or Infor PCM Document Automation can now be attached to records on certain SyteLine forms. Select a record and click the Display Documents toolbar icon to open the Attached Documents form, which lists the Infor PCM documents related to the record. MFG Detail rules or SyteLineDocument integration rules must first be defined in Infor PCM Design Studio in order for the documents to be generated.
For more information about which rules generate documents that are attached to which forms, see the help topic Attaching Infor PCM Documents to SyteLine Records.
You can place a configuration on hold within Infor PCM, waiting for approval or some other confirmation. Now, in SyteLine when you select a record for which the configuration is on hold, the label on the Configure button changes to Configure-HOLD. In addition, the new Config Hold check box is selected. These changes occur on these forms:
Any jobs that are sourced from an order line where the configuration is on hold cannot be released until the hold is removed. When a configuration is approved, you can either reconfigure the sourced job or order line to remove the hold in Infor PCM, or you can select the Actions>Remove Config Hold menu option in SyteLine. The button label is then updated to Configure-Complete and the Config Hold check box is cleared.
Be aware that, because jobs on Config Hold have a status of Firm, those jobs will be included in planning.
When you use the Actions > Copy menu option on these forms to copy a row, any configuration data that exists for the row is now also copied:
Previously, you had to use the Copy Orders and Estimates or Copy Routing BOM forms to copy configuration data.
We added these new forms and reports so that you can view A/R and A/P balances:
A new payment type of Cash was added on these forms:
The Reference Type for cash payments is Cash PMT.
We also added Cash as a new Bank Rec Type on the Bank Reconciliation Report form.
A new Factor check box on these forms indicates if the A/P payment was used during a factoring process:
Because you might both buy from and sell to the same company, we now allow a connection, or mapping, between a customer number and a vendor number. You can define a default offset account to use when you need to offset selected A/R invoices and A/P vouchers for that company. You can still use the existing SyteLine payment, payment distribution, and posted transaction features.
To support this new feature, we added the Offset Account field, along with description and unit code fields, to the Accounts Payable Parameters form. On the Vendors form, we added a Customer field that you can use to map a customer to a vendor when they are the same company.
Use the new AR/AP Payment Offset form to create offsetting payments for A/R and A/P. When you select a vendor or customer number on this form, the outstanding vouchers and invoices for that company are displayed. You can then enter offsetting amounts for the various vouchers and invoices. When the amounts are balanced, offsetting payment and distribution records are created. These payments can then be posted through the standard A/R and A/P posting routines. The offset payments cannot be altered; they are only used to offset the ledgers.
On these forms, we added a read-only Offset check box to indicate whether the payment is an offset payment generated from the AR/AP Payment Offset form:
You can now enter A/R chargebacks, distribute them with the payment, and post them during payment posting. To support this feature, we added the Chargebacks and Chargebacks Deposit account fields on the Accounts Receivable Parameters form, along with their description and unit code fields. We added these new forms:
On the A/R Payment Distributions form, we added the Chargeback Amount field and these buttons: Chargebacks opens the Chargebacks form, and Distribute Chargebacks applies chargebacks to distribution records. On the A/R Quick Payment Application form, we added the Chargebacks button, which opens the Chargebacks form, and we added the Chargeback Amount field to the grid.
The Description field in the Material Transactions form now includes descriptions for non-inventory items.
Service order demand can now be created in APS. In addition to specifying planning priority for service orders on the APS Order Priority form, you can now view service order planning details on these forms:
Users of the Outlook integration can now:
A new credit card gateway option, CenPOS, is supported by the SyteLine Credit Card Interface. If your company is implementing Infor e-Commerce as a Web storefront for SyteLine, the CenPOS gateway is required in order to process credit card payments from e-Commerce through SyteLine. When e-Commerce is not involved, you can use any supported gateway for credit card processing in SyteLine. With CenPOS, all credit card data is entered directly into the CenPOS gateway server.
When you specify CenPOS as the Credit Card System in the Credit Card Interface Parameters form, you must also click a link on that form to configure an encrypted SQL connection to the application database. This connection information is stored in the SyteLine Web server. When you select Pay with Credit Card for a customer order, the Credit Card Payments form is displayed, as usual. However, with the CenPOS gateway, you click Authorize to display the CenPOS virtual terminal in the new Credit Card Web Payment form. The credit card information that is entered in the virtual terminal goes directly to CenPOS, and CenPOS returns token IDs that are stored in a SyteLine table. If you need to authorize a transaction against a saved card, you simply access the token from CenPOS by selecting the last 4 digits of the card in the Credit Card Payments form and click Authorize to call the CenPOS virtual terminal.
To support this change, we added the new Credit Card Integration Web service that is configured through the SyteLine Configuration Wizard. We added the new Credit Card Web Payment form and updated fields on the Credit Card Interface Parameters form and the Credit Card Payments form.
We added these features:
To support this feature, we added these forms and fields:
Because the Kagami report is no longer needed, we removed the Invoice Type field from the Accounts Receivable Parameters form and the Order Invoicing/Credit Memo form.
To support this feature, we added these forms and fields:
To support this enhancement, we added these fields and forms:
The Withholding Tax Certificate Report and Withholding Tax Certificate Report (Reprint) forms now allow up to 13 characters for tax ID numbers. The font size in some areas on the reports is now smaller so that all the necessary text can be viewed. When you print an Input VAT Report or Sales VAT Register report, tax ID numbers and associated addresses are now included on the report.
We also added the Petty Cash Payments Query and Petty Cash Payment Distributions Query forms.
On the Operation Type Formula Workbench form, you can now click the Retrieve Committed Formula button to copy the committed formula to the Pending Formula field. This lets you modify a committed formula without having to create the formula from scratch.
Links to all forms associated with portal shipping carrier and freight charge calculation were added to the Customer Portal and Reseller Portal tabs of the Portal Administrator Home form. Also, all links were organized into functional groups on each of the Portal Administrator Home form tabs.
The Content Development section of Portal Manager now includes tabs for working with collection definitions and field display formats. Portal developers can use the new Collection Definitions tab to add, edit, and delete collection definitions in Portal Manager, instead of using the SharePoint interface. Similar to the Layouts tab, the new Field Display Formats tab allows developers to work from a list of all field display formats in Portal Manager as well.
In the Configuration section of Portal Manager, we added an option for saving portal configuration settings and an option for loading a saved configuration. This makes it easier to restore or replicate the Infor portals.
Portal developers can create or edit field display formats more easily with the updated field display format (FDF) editor. The updated FDF editor includes these features:
The portals now support use of SharePoint 2013.
For portal developers, new APIs and a server-side global script were added to the portal architecture. The new features provide an export to Excel option for content developers to use, which can export content to CSV- or XML-based Excel formats.
Previously, ION connections could only be made to an entire application database, so we had to provide a workaround to allow for multi-site setups. Now, ION Connect can have connection points to specific logical IDs (sites). To support this change on the SyteLine side, we added a From Logical ID field on the Replication Document Inbox and Replication Document Outbox forms.
ION can use the new IMCS Web service to execute an event in the SyteLine Application Event System (AES), or to invoke an IDO method, from the ION Exit Points Activity type. The IMCS Web service can also be called from any client that can send and receive SOAP messages. It allows parameters to be sent and returned after the event or method has been executed. For more information, see the Infor Mongoose Integrating IDOs with External Applications guide.
The Sync AccountingEntity BOD is now supported withSyteLine.
You can now use sprite images to change the appearance of icons used for tool bar buttons when the pointer moves or hovers over the button. For more information, see the help topic Creating Sprite Images for Toolbar Buttons.
Alternatives are now available to the P and C keywords in the WinStudioRuntime interpreter that allow you to provide formatted values. When you use the new PF (PROPERTYFORMATTED) or CF (COMPONENTFORMATTED) keywords, any input masks on the component or property are applied to the value that is returned. Numeric and date values are displayed with the locale settings applied, rather than in Mongoose internal format. For more information, see the online help for the new keywords.
Previously, you could display both text and a graphic image on a static or button component, but only in an overlapped mode. There was also no vertical alignment of text. Now you can use the new Image and Text component property for static and button components to display both images and text either overlapped or non-overlapped. You can justify the text and image horizontally and align them vertically.
The design toolbox now offers a new Calendar component type. This component displays a calendar similar to the one in Microsoft Outlook. It allows you to view and enter calendar information by day, by week, or by month. For more information, see the help topic About Calendar Components.
Developers can now create a unified user control that can be used in the smart clients and the Web client. The content of the user control is defined in an HTML page that is stored in the forms database. This Web user control can reference assets such as Javascript, CSS, images and other content that can be presented in a Web browser. These user controls require no deployment and are available as soon as they are saved.
With the Web user control, you can choose to define a .NET assembly to facilitate communication between a form and the user control. For more information, see the help topic About User Controls.
We continue to update user interface areas such as menus, toolbars, and buttons in the smart client, smart client via browser, and the Web client, to comply with the latest Infor corporate standards. To make these changes more easily, we have extended and enhanced theme style attributes. For more information, see the help topic About Themes.
Minor changes to forms can now be made at run-time and saved by all users, regardless of their user editing permissions. To allow this, system administrators set a new process default, Allow saving form runtime changes. These changes can include form size, splitter position, and grid column sequence, width, and visibility. For more information, see the help topic Process Default Name.
A lightweight Web client is now available for use with mobile devices, by specifying a Web client URL with the login parameter page=light. Although load times and rendering can be slightly faster in this lightweight Web client, the client also has slightly more limited functionality. (Note: The SyteLine Mobile home pages do not use this parameter.) We have also modified some component types such as the combobox and messagebox to be optimized for use on mobile devices.
In the Web client you can now click a button on the tool bar to open the DataSearch form, where you can search for information stored anywhere in the application. The search results are listed numerically or alphabetically by data source. We also added theme-based coloring on DataViews and DataSearch results in the Web client. For more information about themes, see the help topic About Themes.
These features were previously only available in smart clients.
You can now import and export these types of metadata in the AppMetaData Transport utility:
You can import and export the setup information related to each type. For more information, see the help on the utility.
As part of this enhancement, we also removed the Access As field from the DataViews Setup form.
These changes were made to the Form Control utility:
The FormSync utility has these enhancements:
For more information on these enhancements, see the FormSync online help.
Version 9.00 included these features.
Mongoose Customization and Development
These are some highlights of Infor SyteLine version 9.00:
For details about these and other new features, see the sections below.
SyteLine 9.00 includes these new general features.
This version of SyteLine is compatible with these product versions:
This version of SyteLine integrates with these products:
We made these changes:
For more information, see the Installation Guide.
Click the new DataSearch button on the toolbar to open the DataSearch form, where you can search for information stored anywhere in the application. The search results are listed numerically or alphabetically by data source. For example, you could search for all instances of the text string "Young" across all data sources. The results list every data source in the system where "Young" is found, for example in customers, orders, items, vendors, purchase orders, and so on. You can expand the data source to see a list of every occurrence within that data source. For more information, see the help topic Searching the System with DataSearch. An administrator can use the DataSearch Source Setup and DataSearch Source Filter Setup forms to configure additional data sources (IDOs) to search. To use the DataSearch feature, you must be assigned a SyteLineWB (Workbenches) license.
In the Multi-Site Items, Multi-Site Customers, and Multi-Site Vendors forms at a master site, select an existing item, customer, or vendor record that you want to duplicate in other sites. Then select the new Actions > Multi-Site Copy option to display the modal Multi-Site Selection form. On this new form, you select the sites to which you want to copy the record. When you return to the parent form, a duplicate of the item, customer, or vendor record is created for each of the selected sites.
The forms used to define Application Event System (AES) event handlers and actions are administrator forms that require training and orientation to AES. Now end users, such as purchasing managers or executives, can use the New Workflow Wizard to quickly create workflows (event handlers and actions) for some basic notification scenarios. For example, a purchasing manager can build a workflow to "Notify me when a PO line is created for more than $1000." Users can later view the workflows they created in the new My Workflows form.
As users make simple choices in the wizard, behind the scenes the system is creating the same event handler and event actions metadata as via the standard AES forms. The handlers and actions created through the wizard can be viewed and edited in the standard AES forms, if more customization is required.
In addition, these fields were added to the Event Handlers form to support this feature: Purpose, Triggering Property, and Method To Call.
If you select this new check box on the General Parameters form, then in forms where the Starting and Ending fields are blank, users can just specify the Starting field value, and that value is automatically set as the default value in the Ending field. This saves time if you often run reports, utilities, or activities for a single record instead of a range of records.
The Customers, Vendors, Items, and Employees forms now display tiles on the left side instead of a grid. The tiles provide a quick, easy to read summary of key information. To see the full grid view, drag the splitter bar to the right. (If you prefer to see the grid view when the form opens, you can set the Tile When attribute in Design mode to a value less than 20.)
With the new Paste option on the StdDetails right-click menu, users can paste text from the Clipboard using the menu.
You can now view information from multiple SyteLine sites on these Home forms: Buyer Home, Controller Home, Customer Service Home, Inventory Control Home, Production Planner Home, and Project Manager Home. On the Navigator tab on those forms, select a site group in the new Multi-Site Group field. Then most of the sub-tabs of the Navigator tab will display information for all of the sites in that group. An Earth icon is displayed in the top left corner of sub-tabs that have the ability to display multi-site data. The Earth icon is displayed even if you are not viewing multi-site data. For tabs that can not display multi-site data, no Earth icon is displayed.
On the Customer Service Home form's Navigator tab, the Price/Availability and Interactions sub-tabs have a new Site field. In this field, you can only select sites that belong to the selected multi-site group. Data on these sub-tabs is then limited to the specific site.
A new set of forms allows you to navigate SyteLine though the use of conceptual and logical charts. To see a list of these forms and to access them, select Master Explorer > Optional Modules > Concepts and Overview.
We added code to SyteLine to make it easier for other applications, for example In-Context BI or Ming.le, to collect contextual data.
Previously, online help for WinStudio developers was accessed as a separate Help system, under a the Help > Customizing Forms menu option. Now the WinStudio help is combined with the SyteLine help and can be accessed through the standard help contents, index, and search. In the help Table of Contents, find WinStudio topics under "Developing Forms."
We removed the Javascript menus at the top of help topics; now you can find any Related Topics at the end of each help topic. We removed the long lists of field topics and placed more emphasis on creating related topics that explain how to use each new form. Field-level help is still available on most, but not all, forms through right-clicks, F1 or the Help > Current Field menu options. The Show Help in Internet Explorer option in User Preferences is no longer available.
Help now always displays in your default browser instead of in the Help Viewer window.
A linked form opened from a parent form no longer is displayed under the Forms > Most Recently Used menu. Also, when a child form, such as a linked form or a modal form, is closed, the focus now returns to the parent form, that is, the form from which the child form was launched. Formerly, the focus would return to the most recently active form, regardless of whether it was the parent.
All forms, windows, or dialog boxes that formerly used a "Loading" modal window, including the login dialog box, now simply display a "working-in-background" cursor.
We added this feature.
For A/P EFT Posting, if the EFT format is ABAFILE, the filename format is now EFT + day + month + year + hour + minutes + seconds + the file extension (.aba), so the file is never overwritten.
We added these features.
After customers' payments are deposited in your bank, use the new A/R Payment Import utility to import electronic files from your bank that provide a record of the A/R payments. Then use the A/R Payment Import Workbench form to view, modify, and validate the payment and distribution information so that it is ready to post.
The system supports the import of NACHA CCD formatted bank files, which do not require any user-defined mapping. To import other types of delimited or non-delimited bank file formats, set up mappings between the bank files and SyteLine tables with the A/R Payment Import Mappings, A/R Payment Import Field Mappings, and A/R Payment Import Conversions forms. The A/R Customer Bank Account form links customers with their bank routing and account numbers.
Bank files are saved to an archive path specified on the Accounts Receivable Parameters form in case they need to be reimported or referred to later. You can also use the A/R Payment Import Mappings Query and A/R Payment Import Field Mappings Query forms to find specific mapping information.
For more information, see the help topic Importing A/R Payment and Distribution Data from Bank Files.
You can now generate, print, and post invoices and credit memos in multiple target sites from a base site, crossing a multi-site intranet that is defined in the base (login) site.
Use the new Invoice Builder form to create invoices and credit memos for the base site and the other target sites for customer order shipments and returns. The invoice and credit memo generated by the Invoice Builder are only from shipped and returned customer order lines/releases. The invoice and credit memo are generated based on the target site configurations such as invoice numbering, currency code, etc.
Use the new Multi-Site Invoice Posting form to post invoices for both the base site and the target site.
These new fields were added to support this feature:
We added these Customer Service features.
Within SyteLine, you can now define promotion pricing and rebates that give your customers incentives to buy your products. For details, see the help topic Promotion Pricing and Rebate Programs Overview.
These new forms were added for this feature:
These existing forms have new fields or functionality used with this feature:
You can now allow your customers to approve the shipment of orders, which lets the customer control when revenue is recognized for each shipment. To support this feature, we made these changes:
When you fulfill customer orders, click the new Multi-Site Source button on the Customer Order Lines form to open the new Multi-Site Item Sourcing form. This form lets you determine the driving distance between each site/warehouse and the Ship To address, using the Google Distance and Google Maps APIs. You can use the distance, along with the quantity available at the warehouse and the planned production time, to select the best source site and warehouse for the order. To set up the APIs for use with SyteLine, use the new Integration tab on the Order Entry Parameters form.
The Point of Sale (POS) module was formerly a separately-purchased add-on module. It is now included in SyteLine and does not require separate licensing. You can use the forms in the Point of Sale (POS) module to handle walk-in customer transactions such as customer sales orders, service orders, returns, or rentals. POS includes a logical “cash drawer” that the cashier accesses by logging in and out. Separate drawers are maintained for customer orders vs. service orders. The cashier specifies the amount in the drawer when the drawer is checked out and again during end-of-day processing. The balance in the drawer, taking into account all transactions that occurred, must be reconciled when the drawer is checked in. If the drawer is out of balance, an adjustment transaction is created.
POS transactions for new sales are posted to Accounts Receivable as the sale occurs. Balance adjustment transactions, if needed, are posted during End of Day processing. Because POS transactions are normally walk-in sales, the POS module supports transactions only using your domestic currency. For more information, see the help topic Processing Orders with Point of Sale.
These POS forms are now included in SyteLine:
For customer orders that are paid with a credit card, we now provide a way to specify a ship method, and then calculate the shipping freight charges based on that ship method. You can then ship and invoice the customer order either through standard SyteLine or through the Pick/Pack/Ship process. These ship methods also apply to orders received from the Customer Portal (see the Customer Portal section of this topic for additional information). These new features are intended for use with the Credit Card Interface.
These new forms are included:
These forms have new fields or functionality used with this feature:
The features from the former add-on products for Return Material Authorization Extended Disposition (RMX) and Outside Process Management (OPM) are now built into base SyteLine and no longer require a separate license.
Extended dispositions give you more options after materials are returned from a customer. In the standard process, materials are received from the customer, placed into inventory, and a replacement order is issued to the customer if the item needs to be replaced. After the material is returned to the customer, you record a disposition code for the item that was returned. This disposition code is used mainly for reporting. For more information, see the help topic About RMA Extended Dispositions.
(For more information about OPM, see the Manufacturing section below.)
These new forms were added, many of which are used by both Extended Disposition and Outside Process Management:
These new forms were added for Extended Disposition:
These existing forms were updated to include Extended Disposition features:
Previously, the Pick/Pack/Ship and Order Shipping features were completely separate and were not aware of each other. Now, each knows what has been done in the other. Also, the Qty Ready field was added to the Pick Workbench form to support this update.
In addition, we added some functionality to the Shipment Master form for use with Infor QCS, similar to the existing functionality in the Order Shipping form. Order Shipping was changed to only use COCs that are not linked to a shipment\line. The Shipment Master now only use COCs linked to a shipment\line.
Select the new Use Alternate Net Price Calculation option on the Order Entry Parameters form to use a different calculation method for extended net price on customer order lines and estimate lines. This alternate calculation rounds before calculating the price, which in some cases could result in less accuracy than the standard method.
On the Customers form, you can now specify a maximum credit amount per order for the customer. When the Order Credit Limit value exceeds the total available customer credit, what happens next is determined by the setting of Allow Over Credit Limit on the Customer Order Lines form:
The same logic is applied on the POS Entry form for point-of sale orders.
The order credit limit is also displayed on these forms:
In addition, the Validate Order Limit field was added to the EDI Customer Profiles form.
The Customer Purchase Order number field throughout the system was increased from 22 to 25 characters.
You can now filter project, job, customer order and RMA transactions by customer on the Transactions sub-tab, under the Navigator tab on the Customer Service Home form.
You can now create a cross reference to a new purchase order requisition when you create an estimate line. On the Estimate Lines form, select Requisition in the Source field, save the record, and click Source.
We added a warehouse range to the options on the Order Status Report. Use the warehouse range to limit the customer order lines that are displayed on the report. The warehouse is then printed on the report output.
We added a Print RMA Line Reason option that lets you include on the RMA Verification Report the reason why the material was returned. The reason is specified on the RMA Lines form.
We increased the number of decimal places to eight for discount percentages on customer orders and customer order lines. Previously, the number of decimal places in these areas did not match.
We changed the tax code fields on these forms so that the data defaults from the Prospects form now instead of the Tax Systems form.
We removed the use of Data Collection license, as well as the Web DC front-end processor and the DCBackground processor. The underlying data collection storage tables are preserved, so you can use another application to place transaction data into the SyteLine tables. In place of the old DCBackground processor, we now allow you to select and run individual background tasks to automatically post different types of data collection transactions from the DC tables. The Data Collection Parameters form includes a new Background tab where you can set up and run the individual background tasks. The data collection error processing forms work the same way as they did previously.
Fields related to the DC front end processing were removed from the Data Collection Parameters form, the Reset DC Shutdown Polling and Background Status field was removed from the Crash Recovery form, and the DC Web Menu field was removed from the Users form. In addition, these forms were removed: Barcoded Reader Menu Report, Barcoded Intermec Utility Report, Generate Antares Configuration, Physical Inventory Error Processing, Physical Inventory Error Processing Query, Reader Configuration, Reader Configuration Query, and Validate Antares Configuration.
We added these financial features.
Use the new costing analysis feature to create "what-if" costing scenarios and analyze the impact of these changes on your business costs. For example, you could evaluate what would happen based on fluctuating commodity costs, changing direct labor rates, changing component material costs, replacement of labor with machines, or replacement of an expensive component with an inexpensive one. For more information about this feature, see the help topic Costing Analysis Overview.
These new forms and reports were added for this feature:
Also, Costing Alternative fields were added to the Change Cost Rates and Substitute Bill of Material Components forms.
SyteLine provides Multiple Financial Sets of Books (Multi-FSB) functionality for businesses that require reporting for one or more ledgers in addition to the General Ledger. Each new ledger can contain any combination of a fiscal calendar, chart of accounts, and currency that are different from those used for the standard General Ledger. Each combination creates a separate financial set of books, and you can set up as many as you need. For more information about this feature, see the help topic Multiple Financial Sets of Books Overview.
These new forms and reports were added for this feature:
If you assign dimensions to accounts, your G/L data becomes multi-dimensional. For example, not only can you drill down to detail about an account, but you can also drill across to details about the customer or the item involved in a particular A/R transaction posted to that account.
To support this, SyteLine now includes these predefined dimensions that can be attached to an account: Customer, Item, and Vendor. Each dimension has a predefined set of attributes. (Your system administrator can modify or add dimensions and attributes, and set up joins between database tables, to meet your company’s needs. For more information, see the help topic Creating Dimensions and Attributes for Extended Data Analysis.) The Chart of Accounts form now has a Dimensions tab where financial personnel can assign one or more dimensions to an account. Use the Chart of Accounts Dimension Details form to see a list of the attributes included in a particular dimension. Use the Chart of Accounts Dimensions form to see the attribute data that is available for a particular account and dimension. The new Chart of Accounts Dimension Query form is also available.
For more information, see the help topic Specifying Dimensions and Attributes for G/L Accounts.
Previously, control accounts were removed from the drop-down lists of accounts on transaction forms such as Job Material Transactions and Purchase Orders, but users could still manually enter the control account numbers in those fields. Now, if the Secure Control Accounts field is selected on the General Parameters form, users cannot manually enter control account numbers in transaction forms.
However, a user who is assigned the new group authorization Allow JE to Ctrl Acct (Allow Journal Entries to Control Account) can enter a control account for a manual journal entry in the General journal or a user-defined journal in the Journal Entries, Import Journal Entries, or Journal Builder forms. This allows the correction of Distribution journal entries that were incorrectly assigned to control accounts. Control accounts are included on the drop-down lists of accounts in setup and parameter forms.
Use the new Recurring Journal option on the Journals form to designate a user-defined journal as a recurring journal. Entries in this type of journal can be posted every month, or other recurring period, by simply changing the date. For more information, see the help topic Creating and Posting Recurring Journal Entries.
The Positive Pay file, which can be created through the Positive Pay File Generator form, includes a Void field that indicates whether a payment is valid or voided. You can use two fields on the Positive Pay Format Fields form to set this value in the file. Use the new Valid Indicator field to add a code that indicates a valid payment. The previously-named Indicator field was renamed as Voided Indicator; use it to specify a code that indicates a voided payment.
We added two fields to the grid on the Journal Entries form: Customer/Vendor number and Name. These fields show the customer or vendor number and name that are associated with the transaction. You can now export this information with the other grid columns.
You can now indicate on the Items form whether a manufactured item is Subject to Excise Tax, and what percentage of tax is to be collected. The tax is reported on the new Item Excise Tax Report. On the Customer Ship-Tos form, you can indicate whether a customer's orders are to be included on the report. This feature is intended for use with IRS Form 720, where excise taxes on manufactured medical devices are reported and paid by the manufacturer.
Unit code summary/detail can now be printed on the Total Inventory Value by Account report, Total WIP Value by Account report, and Project WIP Value by Account report.
You can now print summary balance amounts for a range of unit codes on the General Ledger, Unit Code Where Used Report, and Trial Balances forms.
On the General Ledger form, you can now use these fields to define a secondary sort method: Transaction Date, Transaction Number, Unit 1, Unit 2, Unit 3, and Unit 4.
General ledger account information now displays on the Generate A/P Transactions and Voucher Builder forms. The accounts that are displayed were entered on the General tab of the Purchase Order Lines form.
We added these fixed assets features and enhancements.
You can now set up a fixed asset with partial depreciation; that is, when an asset is placed in service in the middle of a calendar year or fiscal year, part of the full-year depreciation can be taken in the first year, and the rest in the last year of the depreciation. To support this, the Date to Start Depreciation field was added to the Fixed Assets form, and the Partial Depreciation Type was added to the Fixed Asset Depreciation Tables form. The Fixed Asset Cost Report, Fixed Asset Current Depreciation Report, and Fixed Asset Disposal Report now include the date to start depreciation. For more information, see the help topic About Partial Depreciation.
The Asset Class field is now displayed on the Fixed Asset Costs form, Fixed Asset Depreciation form, and related query forms.
When the Useful Life value is changed on the Fixed Assets form, the system now asks if you also want to update the # Units to Depr field on the Fixed Asset Depreciation form.
Fixed assets and purchase orders are now linked. You can specify that a PO is for a fixed asset. Then on the PO line, you specify the fixed asset code for a non-inventory item. When a fixed asset item is saved on the PO line, a record for that item is automatically created in the Fixed Assets form, with the available information from the PO line. The fixed asset related to the Class Code is used for G/L accounts. You can also create a purchase order using information that you already specified on the Fixed Assets form.
To support this feature, these forms now include a Fixed Asset Number field, an FA Class Code field, and a Department field: Purchase Order Lines, Purchase Order Builder, Purchase Orders Quick Entry. The Fixed Asset Costs form has a new Create Purchase Order button which opens the Purchase Order Quick Entry form.
We added these inventory control features.
With the new Multi-Site Bill of Material Builder form, you can easily copy an item’s BOM from one site to other sites. This requires a replication rule between the sites using a new replication category called Multi-Site BOM Builder. The builder copies current and single level BOMs.
You can now define hazardous material (HAZMAT) compliance programs on the new Compliance Programs form. For each low-level item, you can now specify this information on the Items form: Compliance Program ID, Compliance Program Description, and Compliance Changed. When a specification is changed, the new Item Compliance Assignment Utility form processes each item's indented bill of material and sets the item to non-compliant if any item in its bill of material is non-compliant. The Item Detail Report now includes Compliance Program ID and Compliance Status fields.
For more information, see the help topic Managing Item Compliance.
The BOM Bulk Import utility now processes manufacturer and manufacturer item data. Multi-level BOMs can now be imported and exported. You can update the U/M or operation number for imported materials.
To support these new features, these fields were added:
Use the new Resource Sequencing Sort Setup form to predefine sort criteria that you can use on the Resource Sequencing form. The Resource Sequencing form also has new Select and Frozen fields, and new Freeze, Unfreeze and Sort buttons.
You can now process multiple transfer order lines at one time. Additionally, you can split one line into multiple line parts, to allow one line to ship to, or receive from, different locations.
These new forms and fields were added to support this feature:
You now have greater control over items not maintained on the Items form. You can specify information about these items on the new Non-Inventory Items form. Non-inventory items can be used in many areas of the system, including customer and vendor orders, jobs, estimates, and service orders. The new Non-Inventory Items Query form was also added.
After you change an item product code on the Items form, if you have the proper permission, a popup window gives you the option to automatically update the Account Code field on the Item Stockroom Locations form to match your product code change. If you do not have the proper permission, the popup window reminds you to update the Item Stockroom Locations form manually.
The Material Transactions Report now prints the item description for non-inventory items. (Previously, only descriptions for items defined in the Items form were included on the report.) If a non-inventory item is specified on a purchase order line, customer order line, job material, project resource, or RMA line, you can specify an item description.
The system determines which item description to use based on the type of item:
We added a Print Item Overview option to these reports: Order Verification Report, Packing Slip, Reprint Packing Slip Report, Consolidated Invoicing, Order Invoicing/Credit Memo, Print Price Adjustment Invoice, RMA Verification Report, RMA Credit Memo, Print Delivery Order Packing Slip Report, Print Delivery Order Pro Forma Invoice Report, and Estimate Response Form Report.
If you select this field, the Item Overview value from the Items form prints on the report for each item. Only the first 100 characters are printed. The Item Overview field is supported as a multi-lingual field, so that it can be printed in the customer's language, if a string has been identified in that language on the Multi-Lingual Item form.
Previously, when information related to a transfer order line was changed, a record of those changes was not maintained. The new Transfer Order Lines Change Log provides a list of information related to a transfer order line. When a change is made to the ordered quantity, U/M, scheduled ship date, scheduled receive date, or transit location, the change is recorded.
The Transfer Order Line Items form and Transfer Orders Quick Entry utility now have the Actions menu and right-click menu option List Change Log, which launches the change log as a linked child form.
Use the new Delete Transfer Order Line Item Log Entries utility to delete log records within a specified data range. Optionally, create an initial log entry for each item after deletion.
We added these manufacturing features.
Use this feature to track and ship materials from a standard SyteLine job that are sent to an outside vendor for plating, finishing, painting, or any other service. Previously, OPM was a separately licensed add-on product. Now this feature is built into base SyteLine. For more information, see the help topic About Outside Process Management.
In addition to the new forms listed in the Customer Service section above (under Extended Disposition for Returned Items), these existing forms were updated to include OPM features:
The Job Operation Status Report form now displays the Planned Yield and Actual Yield values for each operation.
This new Material Use Up Report helps you determine the best date to change a part in a bill of material. In many cases, you might want to use up the current inventory of a part before you replace it with a new part. With this report, you can either calculate when the quantity will reach zero, or calculate the remaining quantity at a selected break date.
To support this, we also added information and buttons on existing forms:
The Units forms that were previously in the Field Service (FS-Plus) optional module were moved to the Shop Floor Control area of SyteLine and no longer require a separate license.
These forms are now included in base SyteLine:
Those forms are now included in the Shop Floor Control default authorization group, as well as the SyteLine Service group. They can be accessed either from the Shop Floor Control area or the Optional Modules > Service area of the Explorer. Use of the Units forms is described in the help table of contents under Optional Modules > Service > Units.
We added these material planning features.
These new APS forms let you better analyze alternative planning scenarios: Alternative Summary APS, Alternative Summary Scheduler, What If Scheduler Setup Matrix, and What If Planner Order Priority.
In addition, a new Alternative field was added to the Delete Shift Exceptions and Planning Detail APS forms, and a new ATP/CTP button was added to the What if Demands form.
The new Consolidated Plans APS form enhances the consolidation process and the view of consolidated PLNs in the output data for APS planning.
In addition, two new fields were added to these forms: Planning Parameters, What If Planning Parameters, and What If Items. The Sequenced Component Plans for Mfg Item Safety Stock field eliminates the need for the mfgss2.txt file. If you select Days Supply Planning, planning takes place in two phases. PLNs are consolidated between the phases, and the consolidated PLNs are added to the original requirements for the second planning logic phase.
The Capable to Promise (CTP) process now allows the calculation of projected completion dates through a new CTP button on the Estimate Job Orders form.
In a multi-site SyteLine environment, APS plans each site according to its planning priority. During this process, planned transfers between sites (XFDs) may be generated. Previously, in some cases, these transfer orders were created at sites that had already been planned during the multi-site run. The XFDs were handled by incremental planning, but only after supply swapping, safety stock preservation, and exception logic had already completed - so the XFDs were not accounted for in these actions.
Now, post-processing is deferred at all sites until after all XFDs have been planned.
When you access SyteLine through a Web browser, you can now use the Resource Gantt Chart APS, Resource Gantt Chart Scheduler, Demand Detail Chart APS, Demand Detail APS, Plan Detail Chart, and Plan Detail forms.
On the Resource Gantt Chart APS form, you now perform highlight management, data selection, and operation editing through these new forms: Gantt Highlights, Resource Gantt Chart Selections, Select Gantt Data, and Gantt Edit Operations.
The new Demand Detail Chart APS and Plan Detail Chart forms combine features from the existing Demand Detail and Resource Gantt Chart forms, to help you better visualize planning data.
The APS planning process can now consider multiple warehouses within a single site. All manufacturing is associated with the default SyteLine warehouse. The remaining (distribution) warehouses each have a beginning on-hand inventory level by item and a transit time to/from the default warehouse. Demands for items at distribution warehouses are reconciled against existing available inventory and any future supplies. Unsatisfied demand will result in the planner creating planned intra-site transfers to meet the demand. The planner can now consider supplies at distribution warehouses when fulfilling demand. The APS planner maintains safety stock levels for the default warehouse and each distribution warehouse. For more information, see the help topic About Intra-Site Transfers.
To support this feature, these new forms and fields were added:
You can now set up rules that automatically split planned purchase orders for a purchased item between multiple vendors. If no rule is found for an item, the system looks for any rules that were defined for that item's product code. The quantity requested from each vendor depends on the percentage specified for that vendor in the source rule. You can also define rules that split planned transfer orders for a certain item (or for the item's product code) between multiple sites/warehouses. Use the new Source Rules form to define the rules.
In the Material Planner Workbench Generation form, the source rules are consulted when the source for the item is set to Purchased or Transferred and Use Planned Data is set to Yes or No. For more information, see the help topic Creating Source Rules for Planned Orders.
Use the new View Planning Messages form to generate a list of error, warning and blocked messages. You can filter the messages so that you can easily tell which messages are more important, and you can add any missing messages.
Previously, SyteLine provided some exception message control parameters that were not fully honored by the APS Planner. Now, when generating all Move In and Move Out exception messages, the APS Planner now uses the existing PO and Job Reschedule Tolerance Factors from the Planning Parameters and Product Codes forms.
Also, on the What If Planning Parameters form, the new PO Reschedule Tolerance In/Out and Job Reschedule Tolerance In/Out options give you greater control over which exception messages are shown in alternative planning.
On Hand Below Safety Stock exception messages are now generated only for those items that have a defined safety stock. The safety stock level used when determining these exceptions is not adjusted by negative on-hand inventory levels.
Background task messaging was updated in both single-site and multi-site APS planning. Multi-site planning now reports APS reload errors for all sites, and all planning modes now report the existence of blocked orders.
For those using APS Scheduler, the Resource Gantt Chart form now allows you to use the right-click menu to freeze or unfreeze operations or orders on the schedule. Previously, this feature was only available when the Use Planning Output for Scheduling option was enabled; with normal APS Scheduling, the feature was disabled. Now the right-click menu is also enabled for normal APS Scheduling.
You can freeze the entire job, or operations within a job. The frozen operations are reflected in all Scheduling analysis forms and reports.
We made these changes to the integration:
For more information, see the Infor SyteLine Microsoft Integration User Guide.
We added these procurement features.
The new Purchase Order Lines Change Log form displays the change logs of purchase order lines and releases. A change is recorded if the status, ordered quantity, costs, U/M, due date, or promise date is changed. You can delete these log records with the new Delete Purchase Order Line Item Log Entries form.
The forms Purchase Order Blanket Releases, Purchase Order Blanket Lines, Purchase Order Lines, Purchase Orders Quick Entry, History Purchase Order Blanket Lines, History Purchase Order Blanket Line Releases, and History Purchase Order Lines now have the Actions menu and right-click menu option List Change Log, which launches the change log as a linked child form. Optionally, you can create a log entry for each affected order line.
You can now specify if a vendor is a minority owned business. Use the new Minority Types form to add minority types and their descriptions. Then use the new Minority Owned check box on the Vendors form to specify that a vendor is minority-owned. When this check box is selected, a grid is displayed so you can specify the minority types to which the vendor belongs.
When you print the Purchase Order Report, the buyer's full name is displayed on the report. Previously, only the buyer's user ID was displayed. Many vendors require that the name of the purchasing agent is printed on a purchase order as a point of contact.
On the Builder Purchase Order Report and the Change Order Report, if a user record exists for the buyer and a user description is displayed, that description is printed beside the Buyer label on the report. If a user does not exist or the description is blank, the buyer from the purchase order is printed on the report.
A Recalculate Cost button was added to the Purchase Order Requisition Lines, Purchase Orders, Purchase Order Lines, Purchase Order Blanket Lines, Purchase Orders Quick Entry, Purchase Order Blanket Releases, and Purchase Order Builder forms. Click the button to get the current vendor contract price or the item cost. The system also prompts you with a Yes/No option to update the costs when the vendor is changed.
Use these new forms to account for fluctuating commodity prices and surcharges, across any number of commodity exchange services, on customer and vendor orders:
Each of these new forms has a matching new query form.
Surcharges are measured by comparing the actual and basis pricing during the purchase or sale of affected items. For more information, see the help topic About Surcharges.
A new area on the Vendor Interactions form displays incoming email messages and allows emails to be sent.
We made these project management enhancements.
Use these new fields on the Copy Projects form to specify what information to copy for a project or estimate project: Copy Tasks, Copy Resources, Copy Revenue Milestones, and Copy Invoice Milestones.
You can now track the changes made to a project. To use change order tracking, select Tracking on the Project Types form, then select Track Changes on the Projects form when you create a new project. The new Project Change Orders form tracks project changes. Use the new Project Change Order Detail Report to view a detailed summary report of all the changes made to a project. For more information, see the help topic Tracking Project Changes.
We made these changes in the Sales area.
On the Salesperson Home form, the Prospect Interactions and Contact Interactions sub-tabs on the Navigator tab now behave more like the Customer Interactions tab. You can now choose an interaction in the Interaction field on both tabs. These new read-only fields are now shown on each tab: (Interaction Description), Topic, Prospect or Contact, Company, Status, Interaction Date, Follow-Up Date, Site, and Interaction Salesperson.
On the Receivables sub-tab on the Navigator tab, the right grid only shows accounts receivable data where the current salesperson is tied to the customer order associated with the posted AR transaction.
On the Salesperson Home form, links have been added to the Dashboard tab to open the Sales Forecasts form, the Campaigns form, and the User Calendar form. Links have been added to the Tasks tab to open the Task List form and the Inbox form.
On the Prospects form, use the new County field to specify a county for the prospect address. The new Codes tab on that form contains tax code fields.
On the Prospect Interactions Report and Sales Contact Interactions Report forms, use the new Sort By field to sort by interaction date, follow-up date, entered by, or topic. We also added range fields for interaction number and date.
The Prospect Interactions and Sales Contact Interactions forms are now designed to work more like the Sales Interactions form.
On the Delete Prospect Interactions and Delete Sales Contact Interactions forms, we added range fields for interaction number and date. You can now add attachments when sending emails on the Customer Interactions, Prospect Interactions, Sales Contacts Interactions, and Vendor Interactions forms. New Send Attachments and Send Internal Attachments check boxes are added to those interactions forms.
We added these features for system administrators.
We made changes to the schema and to various areas in the application to allow you to define multiple sites within a single SyteLine database. Now you have a powerful set of options for widely distributed or very centralized management of your sites. (If you plan to use multiple sites per database, SQL Server Enterprise Edition is required.)
Below is a brief list of the changes that were made. For a more detailed list of changes that you should be aware of if you are currently using a version of SyteLine previous to 9.00 with custom tables or coding, see the white paper Coding and Schema Changes Made in SyteLine 9.00 for Multiple Sites per Database.
The Replication Categories form has a new Retain Site field. If this field is not selected for a table, then replication triggers change the site_ref of the target site to the target site value and set the RowPointer column value as a new GUID.
Also, the To object name from Replication Objects is now supported in transactional replication. Previously, it was only supported in non-transactional replication.
The Configuration Manager utility now includes a Site field. Use this field to set the site name, which is then stored in the configuration XML file. If no site is specified, then when a user session is initiated, SyteLine checks to see if there is only one record in the parms_mst table. If so, then it defaults a site value, allowing the session to initiate without specifying a site.
Any third party code that makes SQL server connections must include a way to set the site when initializing context.
You can now define dimensions and attributes for your SyteLine data. For example, financial personnel might want to use multiple dimensions to analyze the Chart of Accounts and posted ledger transactions. Some dimensions (Customer, Item, and Vendor) and attributes for those dimensions have been predefined, but the system administrator can create additional dimensions and attributes, or modify the predefined versions.
Use the new Dimension Table Joins form to link the appropriate primary and secondary tables to the base table (in the example above, the chart table). You can then use the Dimension Attributes form to add columns from the base, primary and secondary tables to the list of attributes for a dimension. (An attribute can be any valid SQL statement used in a SELECT clause within the scope of the table joins.) Use the Dimension Functions form to specify constants, SQL functions and math operands that can be used to add calculated fields to the list of attributes. The new Dimension Attributes Query and Dimension Table Joins Query forms are also available.
For more information, see the help topic Creating Dimensions and Attributes for Extended Data Analysis.
Within the SyteLine application, we added Form Sync and Form Control forms that perform most of the functions that were previously available only in the Form Sync and Form Control standalone utilities. This allows administrators in Cloud deployments to use these functions.
Note: The original Form Sync and Form Control standalone utilities are still available. Due to the transactional nature of using the IDORuntime service to execute SQL statements directly, the existing client versions of these utilities are still required to perform some functions.
In the Form Control form, the runtime and master are based on the configuration you are currently logged into, and your ability to use SourceSafe is limited by the IDORuntime Service capabilities.
In the Form Sync form, you can select both the source and target configurations from the form; your choices for synchronizing non-base level forms are limited to either keeping the customized version or replacing it with the new base level version; and you cannot edit objects such as event handlers or form scripts to merge the two. The Form Choices and Form Sync Log forms were also added to support this utility.
For more information about how the Form Sync and Form Control utilities are used within the application, see the help on these forms.
For situations where you have a new form or object that you have not yet checked in to the master database, there is now an option to display these, along with an indication that they are new, in the display list on the My Checked Out Objects tab. You can also then check the new forms and objects in from the same list on that tab. In addition, the LockedBy status of a form or global object is now supported for global objects, as well as forms. In addition, LockedBy is now more strictly enforced.
Form Control now recognizes bitmaps and drag images that are in the Images table and add them as global referenced objects. Use the new Utilities tab to synchronize the Device Types information between the development and forms databases. Forms can have multiple layouts for different device types, for example, phone vs. tablet vs. laptop. This data should change rarely; however, if you make a change in either the development or the master forms database, you must synchronize the changes between the databases. Otherwise, Form Control displays a warning message during operations if it detects that the Device Type data is not synchronized.
To handle the new form inheritance feature, Form Control maintains the Base Form Name when checking in or out a form that inherits from another form.
Themes are treated as a new global object. All pertinent styles and attributes are copied when working with a Theme object.
Form Sync now handles images as a global object type. The Compare Objects tab allows quick comparison of hashes for images, comparison of the Base64 encoded blob or visual comparison of the images. Form Sync now warns you of conflicting overrides or conflicting customized versions of device types. Form Sync allows you to keep or prompt for ImageSize, Tiles, Themes, DragImage and drag events separately.
To handle the new form inheritance feature, Form Sync verifies that BaseFormName is consistent between customized and vendor forms.
Form Sync also now warns if there are any differences between a theme and its underlying objects (styles and attributes), and it lets you keep the customized theme or replace it with a new vendor theme.
Previously, when a named user license key was in place, a user could log in only once, even if multiple sites were shared through the master site shared users and intranet licensing. Now, in that situation, a user can log in once per shared site.
We changed the way the User Authorization Report can be filtered and organized, so that it is more useful to system administrators and auditors. Now, user and group authorizations for forms and IDOs are grouped together by user ID. Row authorizations are grouped together by user ID and group name, and are sorted by IDO and group name. In addition, new options on the form let you choose the specific forms or IDOs you want to see in the report. You can easily see and compare all authorizations for a single user in the same section of the report. For example, this makes it easier for you to determine whether a user has multiple permissions set differently for the same form, through different groups to which the user is assigned.
A link to open the Recommended Patch Analysis form has been added to the System Administrator Home form.
User-defined record cap overrides are now allowed to persist (be saved) from one session to the next, so users do not need to reset preferred record caps every time they log in. System administrators can use the new process default Disable record cap override save to enable or disable this feature, which is enabled by default. For more information, see the help topic Default Name, Process Defaults.
Session recovery is now available in Mongoose services when an exception happens in a Load Collection or Invoke method during an ongoing open session. This allows the services to resume processing if there is a temporary interruption in communications with the IDO layer.
On the Replication Categories form, we added a new default category, Initialize _All Parameters. We also added a new Replication Category field and a Select By Category button to the Update _All Tables form. During replication setup, you can select this category and click the button to quickly select all of the parameter tables. Previously this was a manual step where you had to select each parameter table separately, which was time-consuming and error-prone. For more information, see the section on Setting Up Replication in the Multi-Site Implementation Guide.
Process default names have been updated for a more consistent presentation in the interface.
The Timer now allows you to set an interval as small as one second. The previous minimum, other than zero, was five seconds.
We updated all of the mobile forms with new icons, and added these features.
Users of mobile forms can now view data from multiple sites. Because of the implementation used behind the scenes, two access methods are used. Some forms include a Site drop-down where users can switch sites to display data from a different site. Other forms include a drop-down with a Switch Site link. Select a configuration from the drop-down list and click Switch Site to log out of the current configuration and log into another configuration, while preserving the current form and filter, if applicable. A login window is displayed, unless the user is set up for Workstation login; in that case, the switch happens seamlessly. The Site and Switch Site components are not visible when you open the form from a standard client.
All mobile Home pages now include a Sign Off button.
The IT Home page and Production Supervisor Home page now use icons, similar to those used in the Executive, Controller, and Sales home pages. All other IT and Production Supervisor mobile forms now include a toolbar instead of Next/Home/Prev links.
Forms designed to work with mobile devices now use larger toolbar buttons, to accommodate finger taps.
General information about SyteLine portal updates is listed here. For more details about portals, see the Portal Setup and Administration Guide.
The Customer, Vendor, and Reseller portals can now connect to multiple sites in SyteLine, to display and update data from these sites. To set up this feature, configure the primary site in Portal Manager and create a portal site group in SyteLine. The primary site is where key data is maintained by SyteLine users, such as items and item categories. The portal site group includes the primary site and all other sites whose information should be available to the portals.
We also provide a User Account Management Utility page in the Customer, Vendor, and Reseller portals. Administrators use this page to create portal user accounts across all sites in the portal site group, copy portal-enabled user accounts from the primary site to all other sites, or troubleshoot problems with portal user account setup.
We made these enhancements to the Customer Portal in this release:
These new SyteLine forms were added for the Customer Portal:
These SyteLine forms were updated:
These new portal pages were added to the Customer Portal:
In addition to the new user interface, these updates were made to portal pages:
These new SyteLine publications for the Customer Portal were added:
Updates to the Vendor Portal include an updated user interface and multi-site support.
SyteLine 9.0 includes the new Reseller Portal, which has been developed for your customers who are also set up as resellers in SyteLine. In addition to new reseller-specific portal pages, the Reseller Portal includes all of the pages from the Customer Portal, many with additional functionality for reseller tasks. For example, Reseller Portal users can place orders, check order status, and look up estimates for themselves or for their customers by posing as a selected customer.
These new SyteLine forms were added for the Reseller Portal: Unit Registration Posting and Search for Unit Registration Posting.
These SyteLine forms were updated:
These new pages are included with the Reseller Portal:
These new SyteLine publications and workflow event handlers were added with the Reseller Portal:
Event Handlers:
Publications:
The portal architecture includes these enhancements:
The Portal Manager includes these enhancements:
We made many changes to optional or "add-on" modules.
These former add-on products that were separately licensed are now incorporated into base SyteLine and are now accessed with standard SyteLine licensing:
Click on the links above to see overview information about the new features.
These products still require a separate license but are now installed with SyteLine:
Help for these modules is now available from the SyteLine Help Contents > Optional Modules.
This new form lists the licensed optional modules that are available by site. A system administrator must use this form to enable the base SyteLine features of optional modules for a specific site, after the modules are licensed for the database. For more information, see the Licensing guide, section on Licensing and Enabling Optional Modules.
The China localization is now installed with base SyteLine but requires a separate SyteLineCN license. The forms are now included in the new China Country Pack authorization group.
The Japan localization is now installed with base SyteLine but requires a separate SyteLineJP license. The forms are now included in the new Japan Country Pack authorization group.
Some forms that were in the previous version of the localization were removed, and the relevant fields were added to base SyteLine forms. On the Customers form, new fields are: Consumption Tax Header Line Method and Consumption Tax Round Method. On the Accounts Receivable Parameters and Order Invoicing/Credit Memo forms, the Invoice Type field was added, allowing you to choose a Standard or Japanese invoice.
The Mexico localization is now installed with base SyteLine but requires a separate SyteLineMX license. The forms are now included in the new Mexico Country Pack authorization group. Some forms that were in the previous version of the localization were removed, and the relevant fields were added to base SyteLine forms.
These fields were added to existing forms:
These new forms were added:
Note that the Electronic Invoice for Mexico is still downloaded separately with the country pack.
The Thailand localization is now installed with base SyteLine but requires a separate SyteLineTH license. The forms are now included in the new Thailand Country Pack authorization group. Some forms that were in the previous version of the localization were removed, and the relevant fields were added to base SyteLine forms.
These fields were added to existing forms:
These new forms were added:
The Credit Card Interface, which was formerly a separately installed add-on product, is now installed as part of SyteLine. However, a SyteLineCC license is required to access the forms. Information about the forms is included in the SyteLine online help.
Use the Credit Card Interface to bill a customer's credit card through a third-party credit card processing service to accept credit cards for payment. The credit card is authorized for validity when an order is placed, but it is not charged until the order is shipped and the invoice is posted. During the invoice posting process, if the credit card charge is successful, the system automatically posts and applies the payment to the applicable invoice.
The interface communicates with a Gateway provider such as Intrix or TGate, which in turn communicates with the credit card processing company such as Visa or Mastercard. (See the Credit Card Implementation Guide for a list of supported Gateway options.) To preserve security, this application does not store any credit card information; it only stores a transaction number that links to the Gateway provider's application.
These forms were added to SyteLine but can only be accessed if the site is licensed for the Credit Card Interface:
These forms now include a Pay with Credit Card button:
In addition, the Distributions and Quick buttons on the A/R Payments form are disabled if the site is licensed for the credit card interface and the A/R payment is a credit card payment.
For more information, see the help topic About the Credit Card Interface.
The Printing Industry Pack is now installed with base SyteLine but requires a separate SyteLinePP license. The forms are now included in the new PP Ind Pack authorization group. For more information, see the help topic About the Printing Industry Pack.
The product name was changed from Infor Field Service-Plus (FS-Plus) to Infor SyteLine Service. We added these new license modules: SyteLineFSP, SyteLineFSP_MS (multi-site), SyteLineFSPM (Plant Maintenance), SyteLineFSPM_MS (Plant Maintenance multi-site), and SyteLineFSP_DC (data collection). The forms in the SyteLine Service optional module, and the SyteLine Service-dependent features in base SyteLine, are assigned to one or more of those licenses.
These replication categories were added to base SyteLine: SRO Copy, Global Incident, Global Service History, Global Units, and Global Scheduling of Shared Partners.
These new default authorization groups were added to SyteLine to include the SyteLine Service forms: SyteLine Service, SyteLine Service Outlook, FS-Plus Sched Public Profiles, and FS-Plus Sched Public Filters.
An additional journal, FS Dist, was added.
The Units forms that were previously in SyteLine Service are now included in base SyteLine. See the Manufacturing section of this topic for more information.
These form names were changed:
| Field Service-Plus | SyteLine Service |
| Event Codes | Incident Event Codes |
| Insert Incident Information | Incident Quick Create |
| Service Inspection Measurement Types | Inspection Measurement Types |
| Service Inspection Section Codes | Inspection Section Codes |
| Service Inspections Setup | Inspections Setup |
| Service Inspection Tasks | Inspection Tasks |
| Service Inspection Types | Inspection Types |
| Service Approval Console | Inspector Workbench |
| Partner Expense Report | Miscellaneous Expense Report |
| Multi-Site Sro Copy | Multi-Site Service Order Copy |
| Reimbursement Tax Detail | Partner Reimbursement Tax Detail |
| Activities | Service Activities |
| Schedule Appointments | Service Appointments |
| Appointment Status Codes | Service Appointment Status Codes |
| Appointment Status History | Service Appointment Status History |
| Appointment Types | Service Appointment Types |
| Annual Contract Renewal Listing Report | Service Contract Annual Renewal Listing Report |
| Contract Invoice Listing | Service Contract Invoice Listing |
| Contract Invoicing | Service Contract Invoicing |
| Contract Item Availability | Service Contract Item Availability |
| Contract Lines | Service Contract Lines |
| Contract Maintenance Schedules | Service Contract Maintenance Schedules |
| Contract Profit Analysis Report | Service Contract Profit Analysis Report |
| Rental Contract Agreement | Service Contract Rental Agreement |
| Contracts | Service Contracts |
| Contracts Query | Service Contracts Query |
| Contract SRO Generation Utility | Service Contract SRO Generation Utility |
| Contract Status Codes | Service Contract Status Codes |
| Contracts To Be Invoiced Report | Service Contract To Be Invoiced Report |
| Customer Contacts | Service Customer Contacts |
| Contact Query | Service Customer Contacts Query |
| Item/Whse Replenishment | Service Item/Warehouse Replenishment |
| Operation Codes | Service Operation Codes |
| SRO Planned v. Actual Report | Service Order Planned v. Actual Report |
| Automatic SRO Generation | Service Order Automatic Generation Utility |
| SRO Billing Console | Service Order Billing Console |
| SRO Close Utility | Service Order Close Utility |
| SRO Labor Costs | Service Order Labor Costs |
| SRO Labor Data Collection | Service Order Labor Data Collection |
| SRO Material Data Collection | Service Order Material Data Collection |
| SRO Drop Ship To | Service Order Drop Ship To |
| Service Order Estimate | Service Order Estimate Report |
| SRO Outstanding Exchanges Report | Service Order Outstanding Exchanges Report |
| SRO Exchanges To Be Shipped Report | Service Order Exchanges To Be Shipped Report |
| SRO Inspection Report | Service Order Inspection Report |
| SRO Invoice Listing | Service Order Invoice Listing |
| SRO Invoicing | Service Order Invoicing |
| SRO Labor Accounts | Service Order Labor Costs |
| SRO Labor Clock Off | Service Order Labor Clock Off |
| SRO Outstanding Loaners Report | Service Order Outstanding Loaners Report |
| SRO Loaners To Be Shipped Report | Service Order Loaners To Be Shipped Report |
| SRO Margin Analysis Report | Service Order Margin Report |
| SRO On Hold Report | Service Order On Hold Report |
| SRO Operation Code Cost Report | Service Order Operation Code Cost Report |
| SRO Packing Slip | Service Order Packing Slip |
| SRO Packing Slip Generation | Service Order Packing Slip Generation |
| SRO Packing Slip Maintenance | Service Order Packing Slip Maintenance |
| SRO Picklist Report | Service Order Picklist Report |
| SRO Planned Material Requirement Report | Service Order Planned Material Requirement Report |
| SRO Shipment Listing | Service Order Shipment Listing |
| Quick SRO Create | Service Order Quick Create |
| SRO Labor Rates | Service Order Labor Rates |
| SRO Status Report | Service Order Status Report |
| SRO To Be Invoiced Report | Service Order To Be Invoiced Report |
| SRO Transaction Posting | Service Order Transaction Posting |
| SRO Transactions | Service Order Transactions |
| SRO Transactions Additional Filters | Service Order Transactions Filters |
| SRO Posting Information | Service Order Posting Information |
| SRO Types | Service Order Types |
| SRO WIP Valuation Report | Service Order Wip Valuation Report |
| SRO Working Status History | Service Order Working Status History |
| SRO Work Order Report | Service Order Work Order Report |
| Service Outlook Integration Parameters | Service Outlook Integration Parameters |
| Sync Enabled | Service Parameters Sync Change |
| Incident Priority Codes | Service Priority Codes |
| Reason / Resolution Search | Service Reason/Resolution Search |
| Color Coding | Service Schedule Color Coding |
| Schedule Conflicts | Service Schedule Conflicts |
| Dispatch Scheduling | Service Schedule Dispatch |
| Preview Email | Service Schedule Email |
| Label Setup | Service Schedule Labels |
| Multi-Day Scheduling | Service Schedule Multi-Day |
| Multi-Day Scheduling Preview | Service Schedule Multi-Day Preview |
| Scheduling Local Appointments Filters | Service Schedule Local Appointments Filter |
| Service Scheduling Parameters | Service Schedule Parameters |
| Scheduling User Permissions | Service Schedule Permissions |
| Scheduling Filters | Service Schedule Profile Filters |
| Display Profiles | Service Schedule Profiles |
| Schedules | Service Schedules |
| Serials | Service Serials |
| Incident Status Codes | Service Status Codes |
| Contract Service Types | Service Types |
The Emailer Service previously used in FS-Plus is replaced by calls to the Application Event System in SyteLine Service.
Fields and buttons were modified or added on these base SyteLine forms. New fields and buttons are disabled unless the user has the appropriate SyteLine Service license:
In addition, many names of tables, IDOs, stored procedures, background tasks, and report (RDL) files were changed to be standardized for SyteLine.
The Tax Interface is now installed with SyteLine but requires a separate SLTaxInterface license to use. The names of forms, IDOs, background tasks, and so on have been standardized for SyteLine. A new Tax Interface authorization group was added that includes the forms specific to the interface.
These buttons and fields on base SyteLine forms are now enabled when a site is licensed for the Tax Interface; otherwise they are displayed but disabled:
Some of the tools formerly in the Workbench Suite were incorporated into the core Mongoose toolset: DataViews, Critical Numbers, and DataSearch. For more information about how these tools are used now, see the General section above and Mongoose Customization and Development section, below.
The Workbench forms, Navigation forms, and prebuilt sources for critical numbers, DataViews, and DataSearch are only available in the SyteLine Workbench Suite. The Workbench Suite is now installed with base SyteLine. To access either the new core Mongoose tools or the SyteLine-specific forms and sources, you must have a SyteLineWB license. Two new authorization groups separate the operational use of critical numbers and DataViews from the administration. The Workbench User group can view critical numbers and DataViews, and the Workbench Administrator group can modify and create new critical numbers and DataViews. Some Workbench forms are also included in the Service group.
We added these customization and development features.
These areas of BOD integration were improved:
Click the new DataView button on the toolbar to open the DataViews form. With DataViews, you can view, parse, sort, group by, and filter data from the application within user-definable views and layouts. The DataView setup is similar to an Excel spreadsheet, displaying data in columns. As with form personalization, the DataView structure supports user, group, and site level layouts. You can export the DataView as a report to a printer, XPS file, or Excel. Additionally, you can drill down to the related form by clicking Details on the right-click context menu of a DataView. For more information, see the help topic About DataViews. To use the DataViews features, you must be assigned a SyteLineWB (Workbenches) license.
To support DataViews, the StdCurCompSearch event and these form component scripting APIs were added: DataViewGetScopeFilter(), DataViewRefresh(), DataViewDrilldownLoadDetailForm(), and DataViewDrilldownRunSubDrilldown().
In Design Mode, click Form > Definition > New Data Maintenance to use a wizard that helps you create a database table, an IDO with its properties, and (optionally) a form all at one time. With the wizard you can complete simple, two-dimensional forms, for example with no containers such as form pages or notebooks. For more complex forms, use this wizard to build the basics of the table and IDO, and then use the New Form Wizard to perform additional work on the form, for example to add subcollection properties, etc.
After you create the data definitions, you can choose to create a form and/or a script from the data. You can also save your definitions in a template (XML). Use this option to save your changes periodically during the definition, to complete the definition later, or to use it again for future forms. When you select a property class, the wizard automatically sets the Column Data type (SQL data type) and the Mongoose data type. When you define properties with user-defined types, the wizard simply sets that user-defined type and nothing else. The wizard includes help messages that display when you hover over areas of the dialog.
You can now create a form that inherits components, variables, etc., from another form. This can be useful for forms intended for use as styled web pages, where a template defines the base styling and other forms inherit from it. The New Form Wizard (Form > Definition > New) now has an option to extend an existing form - just specify the new form name and the name of the form from which it is derived. When you edit the new form in design mode, a new Base Form Name property specifies the name of the form on which your new form is based. By default, all components, event handlers, variables, and scripts are inherited from the base form. Inherited components, event handlers and variables are read-only by default, but you can set the new property From Base Form to False and then edit them as needed. The Edit Form Script dialog box has a new Base Script(s) tab where you can view the scripts used in the base form. We also added a filtering feature to the Event Handlers list dialog box.
The ways you can select multiple properties are enhanced on the Properties Selection page. The Properties Definition page now lets you create or set string captions for each property. A container and the component’s sequence within that container can be set for each property. Definition of form pages and notebooks is more intuitive. Additional form types of detail-only and tile were added. The wizard includes help messages that display when you hover over areas of the dialog.
A new Message Num Prefix field on the General Parameters form lets you specify a prefix to use with your custom messages, so that you can easily identify your company's messages and distinguish them from system messages. To create and maintain system and custom messages, see the help topic About Message Construction.
All existing SyteLine graphs on forms were converted to use the FusionCharts tool. Two new Design mode controls were added to the toolset to support FusionCharts: Chart and Gauge. You can also use these controls to add custom charts or gauges to your forms. The Gauge component supports the use of critical numbers. Click events are supported at the chart and individual data plot levels (for example, column of a column chart, pie slice of a pie chart, etc). These click events can be handled by specifying a URL to launch or a JavaScript function to execute. (The old graphing tool is still available for backward compatibility.) For more information see the help topic Adding Charts or Gauges to a Form.
The SQL Tables form now provides more options for creating and modifying SQL tables in the system. You can now not only add columns and primary keys, but also add and modify constraints (such as foreign key relationships and indexes), set data types, and create user-defined data types.
You can now store image (graphics) files in the Forms database, so they are more easily accessible from a "cloud" or remote installation. Design Mode now provides a new Edit menu option and an Images dialog box.
We updated these features:
If an inline list or validator is defined on a property, that specification is now inherited by components in WinStudio that are bound to that property, unless a property class extension, component class, or component overrides the inherited list.
We made these improvements:
For each event, the handler is called with a reference to the item that is about to be processed, or that was just processed.
Previously you had to use a wizard to create a new IDO property. Although you can still use the wizard, you can now use the normal New and Copy operations from within the IDO Properties form.
We added critical numbers as a new data source for gauge control. You can now bind a gauge to a critical number. Critical numbers are key performance indicators (KPI) that you can use to track progress. For more information, see the help topic About Critical Numbers. The critical number Email Generation utility now uses the application event system instead of using the external emailer service. To use the Critical Numbers features, you must be assigned a SyteLineWB (Workbenches) license.
Previously, when you specified the parameters for a component class in the Component properties sheet, you had to type a comma-delimited list into the Parameters field. Now you can optionally use the new Edit List of Component Class Parameters dialog box, to manage long lists of parameters, and to build parameters by selecting from drop-down lists of variable, component, and property names used in the current form.
Forms and some types of form components now offer the option to use transparency (alpha) values and linear gradients. You can save background color definitions as global variables for reuse, or you can modify the settings on an individual form/component basis.
You can now use drag-and-drop functionality between components on forms. Two new component standard event properties, Drag From Events and Drop On Events, were created to facilitate this functionality.
We added options to the View menu to hide or show the first (grid fields) pane and second (edit fields) pane, when they are available on a form. You can also use the hot key combinations Ctrl-Shift-1 and Ctrl-Shift-2 to hide or show the panes. On a notebook component, the No Scroll option and tab foreground/background color options are now honored in browsers. The To Excel export option for grids is now honored in the browser. On mobile devices that are displaying a form in a Web browser, the tap-and-hold action is now treated as a contextmenu event for the target element, so the standard right-click menu is now displayed.
The Send Web Container Message event type now supports the use of multiple Web Parts within a single SyteLine session.
The system now supports multiple display formats, including the standard Smart client, Web browsers, and multiple mobile devices, all from a single form. You can set which type of device should be the default display and make variations in different displays based on the type. For more information, see the help topic About Devices and Derived Forms.
This feature allows for the orderly deletion of records when the deletion involves more than one IDO. There are now three options: Restrict, Remove, and Cascade. For more information, see the help topic IDO Deletion Rules.
The Edit Event to Generate dialog box is now enabled with the option to post an event asynchronously. Select this field to complete the current processing, and then generate the event handler.
With form components that allow the use of graphics images, you now have three new options to define how the image displays within the component: Fit, Fill, and Actual.
You can take action when a row in the current collection becomes modified with this new WinStudio standard event. This event is generated only when the user changes the value of a component bound to a property of the current collection or an event handler marks the row or a property modified, and the current row is not already modified. This could also occur on an auto-inserted row that becomes modified, but more typically it would be generated on a row queried using LoadCollection and then modified.
Previously, options for the PROPERTY event parameter function included only PROPERTY( ) and P( ). New options include PROPERTY2( ), PROPERTY3( ), P2( ), and P3( ). Similar new options now exist for the FILTERPROPERTY / FP event parameter function. All options behave in a way similar to their predecessors.
You can now set a default user name on any records created in a session without creating a new session.
You can now incorporate data from non-Mongoose SQL Server databases into your SyteLine application. The new IDO Linked Databases and IDO Linked Tables forms help you to incorporate data sources that do not use the Mongoose table schema.
In addition, Mongoose applications can now communicate with Oracle databases through the IDO layer. A new form, Outrigger Profiles, is used to define a profile for the Oracle database. The profile stored with an IDO definition is used to make an ApplicationDB object within the IDO layer for read and write operations on the table, as well as for method calls to that database. A called Oracle IDO method must be a function with a return type of integer. The standard Oracle client dlls are required on the Mongoose utility server. For more information, see the help topic Including Data from an Oracle Database into a Mongoose Application.
There is now a new process default for use with alphanumeric fields that use an <alphaprefix><numericsuffix> format. Previously, fields that used this format would automatically fill in the space between the alphabetic characters and the numeric characters with zeroes. For example, an alphanumeric field of this format with a length of 10 would display an entry of "T455" as "T000000455". The new NUMSORTCHAR numeric pad process default provides other options for the display of data with fields using this format. For more information, see the help topic Default Names.
Previously, the default value specified on an IDO property was treated as a UI hint only. There was no logic in the IDO layer to use the default values other than when reporting the values to the client. The system now uses the default values specified in the IDO property metadata to ensure that any insert action executed through an IDO includes the IDO property's default value. This applies only to base-table bound IDO properties when the IDO insert request does not include all properties that have a default value defined, or when it includes one or more of these properties, but they are not marked as "modified". In this way, they behave much like a default value specified on a column in the database.
Previously, in form-only mode on a Web client, you had to ensure that only one form was running at a time. A second requested form was loaded under the first form, instead of on top of it. To handle this, developers had to use "goto form," which forced the first form to close before the new form opened. Now a second requested form opens on top of the first form on a Web client, and if you close the second form, the first form is redisplayed.
You can now use a single command to export all metadata objects for a configuration to a set of XML files. You can also use a similar command to perform a mass import of all metadata objects from a set of XML files into a configuration. These options are available as line commands only. In addition, system objects such as application events, event triggers, event handlers, event global constants, and event initial states can now be exported and imported like other IDO metadata.
We compared IDOs and their related stored procedures and corrected any mismatched numbers of parameters, mismatched parameter names, and mismatched parameter lengths.
Two new standard events were added to WinStudio Designer. StdQueryFormInitializeCompleted is generated after initialization is complete, and after the user opens a new saved filter. StdQueryFormClearCompleted is generated after the user clicks the Clear button.
The WinStudio event handler response type of SetValues now supports an option not to mark components and properties modified.