This document supplements the standard Protean ERP Product Release Notes, documentation, and online help, listing customer-reported defects that have been resolved in release 4.1.
This is a *Unicode* release.
The following list contains the changes made to Protean ERP to resolve issues reported to Protean Support. The changes are grouped by product area.
Key:
MSnnnn and Cnnnnnn = These numbers are the tracking numbers provided to customers by the Protean Client Support Services call tracking system.
MARmannnnn (shown in parentheses) = These are the Protean Development Center's internal tracking numbers.
C067479 (MARma54614) Foundation
The View Logs button on the Mass Order Complete tool opens the wordpad.exe (WordPad) program to display the log files. WordPad is used because of the file-size limitation of Notepad. In order for the View Logs button to open the log file, wordpad.exe must be installed on the Protean client or terminal server.
MS5702 (MARma31242) Foundation
Protean online help has been updated to include the following information: If there is an add-on definition associated with an object, you can select the add-on when you create a query definition.
C066065 (MARma54241) Foundation
A new property was added to the Protean session (and Web session) objects. The property is called UserID. For all three login modes, this returns the system user ID entered during Protean login (not the RDBMS user ID).
The user object is NOT returned; however given the UserID, you can obtain the user object by constructing the User reference and opening the User object for review.
C069221 (MARma55265) Foundation
Prior to this fix, when viewing a Seagate Crystal report through Protean, there was no way to display the group tree.
With this fix, the group tree is now available. It is not shown by default, but you can click the Toggle Group Tree button to display the group tree.
C062268 (MARma53083) Foundation
Prior to this fix, you could not remove individual security groups from the workspace. If a security group needed to be removed, it was necessary to remove all security groups and then re-add the security groups you wanted to remain on the workspace.
With this fix, you can now remove an individual security group from the workspace by selecting the security group and then pressing the Delete key.
C066535 (MARma54347) Foundation
When the Protean Security Mode is set to Multiuser, the user ID you enter is actually a Windows user ID. Windows allows user IDs up to 20 characters in length but, prior to this fix, Protean was limiting the user ID to its user ID length of 15.
With this fix, the length of the system ID in the User object has been increased to 20 characters. If you are logging in using Multiuser mode, the length of the User ID field now allows 20 characters which allows you to use any valid Windows ID.
(MARma55426) Foundation
Prior to this fix, the security groups on Protean objects were not exposed through the Protean automation interface, so it was not possible to develop programs that would set the security groups in an automated fashion.
With this fix, security groups are now exposed as properties on all Protean objects. All existing security is enforced. If a user does not have authority to change the security groups, then attempting to set these properties generates an error message.
C026066 (MARma44753) Foundation
Prior to this release, only summary information was captured for objects for which the audit trail was enabled. With this release, detailed audit trail information can now be captured, including the before and after values for each attribute that is changed for an object.
The Detailed Audit Trail feature lets you specify the attributes you want to audit for any of the following objects, and then creates a detailed audit trail when those attributes are changed. The objects are:
1. Characteristic
2. Comment
3. Resource
4. Value table
5. Production model
6. Schedule
7. Vendor resource
8. Classification
9. System tailoring (also called Protean system tailoring)
10. User
11. User group
12. Workspace
13. Lot/sublot
14. User-defined activity type
For more information about the Detailed Audit Trail feature, refer to the Protean Release Notes for Protean release 4.1.
C014138 (MARma42434) Foundation
Prior to this fix, Protean reports could not be launched when using Protean Environments unless a system DSN with the same name as the Environment name was created. Only then could the reports be viewed.
With this fix, Protean reports can be launched when using Protean Environments. A system DSN with the same name as the Protean Environment no longer needs to exist.
C065191 (MARma54112) Foundation
Prior to this fix, letters in text boxes with Umlaut were shown in lower case within Protean 3.2 running on Citrix.
With this fix, the system default locale is set during Protean initialization so that the Umlaut letters are properly uppercased.
MS22116 (MARma30231) Foundation
With this enhancement you can now define tab-level security for the Resource object. To do this, use the Workspace notebook. Note that tab-level security is not available for add-on tabs. For more information about tab-level security, refer to the Protean Release Notes for Protean release 4.1.
(MARma54626) Foundation
Prior to this fix, custom foreign key constraints with names longer than 30 characters were generating SQL errors during Protean database conversions.
The database conversion SQL script was fixed to drop custom foreign key constraints with the maximum allowed length on SQL Server (128 characters).
MS30288 (MARma42551) Foundation
Steps for managing SQL logins while copying and restoring Protean databases across database servers was not clearly documented.
The Protean ERP Installation Guide and the Protean ERP Migration Guide now describe SQL login management on copied Protean databases.
C069980 (MARma55249) Foundation
The Protean database conversion from earlier versions to release 4.0 of Protean could sometimes generate a large output log file called convpost.sql.out.
In Protean 4.1, the dbparms.ini file used for conversion includes a configuration option to turn off performance statistics data collection. Turning off performance statistics data collection in dbparms.ini stops the output log from growing too large during the Protean upgrade.
C069224 (MARma55081) Foundation
Prior to this fix, if the Regional Settings for the Decimal Symbol had been modified, the dot key (.) on the numeric key pad could not be used as a decimal point during data entry in a table, such as in an activity form.
With this fix, users can now use the dot key (.) on numeric key pad to enter the decimal point irrespective of the Regional Settings for Decimal Symbol.
C063107 (MARma53348) Foundation
Prior to this fix, if a user tried to open an object or tool when the object's or tool's Protean module was not installed, Protean would crash.
With this fix, users get an error message that the Protean module needs to be installed.
C068673 (MARma54850) Foundation
Prior to this fix, the Protean Account Maintenance utility (protacct.exe) crashed if a user name with 22 characters or more was entered on the Assigned tab.
With this fix, there is now a 255-character limit on user names.
C067473 (MARma54598) Foundation
Prior to this fix, there was no way to refresh a report and enter a different set of parameters without closing the report window and asking to view it again.
With this fix, the Crystal report viewer has been changed with the upgrade to Crystal Reports 9.0. The viewer now lets you refresh the report directly from the viewer via a toolbar button (that looks like a yellow lightning bolt). Clicking this button opens a prompt dialog that lets you enter different parameters.
C072951 (MARma56337) Foundation
Prior to this fix, when users attempted to reduce the precision of any of the three currency amount types (cost, price, or amount) on the Currency object, they were stopped. However, no warning that they were making an irreversible change was ever provided when they attempted to increase the precision.
With this fix, users who attempt to increase the precision of any of the three currency amount types on the Currency object get a message informing them that they are making an irreversible change, which gives them the opportunity to prevent the increase.
C063300 (MARma53484) Resource Accounting
Prior to this fix, when the Validate Financial Accounts option was selected in the Resource Accounting (RA) posting profile, if an account had an effective date outside the journal effective date range, a critical error occurred during Resource Accounting Summarization, and the journal entries were created and saved with an incomplete status.
With this fix, a critical error occurs during Resource Accounting detailed posting and the RA JELIs is not created. Users can correct the accounts and post the same transactions again.
C021483 (MARma43909) Customer Order Management
Prior to this fix, all messages issued by the Protean ATP action server had the same message number. This prevented users from suppressing the messages that say inventory is sufficient to meet the demand while allowing other messages to notify users when inventory was not available.
With this fix, the ATP action server has been changed to use distinct messages for each type of inventory availability. Users can now disable the messages that display when sufficient inventory exists while allowing messages to display when inventory is not sufficient. The message numbers of the user-defined severity (UDS) messages you may want to review are: 21457, 21458, 21459, 21460, 21461, 21462, 21463, 21464, 21465, 21466, 21467, 21468, 21469, 21470, 21471, 21472, 21475, 21477, 21478, 22169, 22170, 22171, 22172, 21481, 21482, 21483, 21484, 22173, and 22174.
C070278 (MARma55364) Customer Order Management
You can verify that the Protean Forms Service (PFS) is working by dropping a PFS Test document in the Queue directory on the PFS machine. The document should be formatted and printed by the default PFS printer. The test document will move from the queue directory to the printed directory.
You can obtain a PFS Test document by contacting your local Protean Support Center or downloading it from the Protean Support website:
http://support.invensysproductionsolutions.com
MS26050 (MARma39928) Customer Order Management
Protean online help has been updated to include the following information: On the Assignments notebook Condition tab, select None to indicate that the tax categories associated with the tax profile are strictly for order deliveries only.
C071276 (MARma55734) Customer Order Management
Protean online help has been updated to include the following information:
The following Available To Promise (ATP) Protean actions check all the deliveries on a line. If you associate any of these actions with events that are triggered automatically for every delivery, the actions cause each delivery to be checked multiple times needlessly. The ATP actions are:
Check Line Avail - Multi Site
Check Line Avail - Single Site
Chk Is Or When Avail - Multi
Chk Is Or When Avail - Single
To prevent needless checking, when you choose an event to trigger one of these ATP actions, choose an event that occurs: infrequently; when the entire line is affected; or at a user's request (such as the Pricing Requested event, which happens when a user selects Price Line from the menu).
C007228 (MARma41211) Customer Order Management
Protean online help has been updated to include the following information: On the Resource notebook Logistics tab, page 3, the Overshipment Tolerance % attribute's description in online help now indicates that you should specify a blank value if you want to indicate that there is no limit on the overshipment restriction. If you specify a blank value, the Market Profile notebook Shipping Rules tab's values will determine if overshipments are allowed, and the percent or amount that is allowed.
C055282 (MARma50544) Customer Order Management
The following Protean online help topics have been modified to include information about how the shipping sites and geographical zones work together:
Order notebook, Delivery-Level: Shipping Information tab
Market Profile notebook Sites tab
Geographic Zone notebook Basic tab
C063333 (MARma53481) Customer Order Management
Prior to this fix, there was no confirmation or warning message displayed when a user selected to cancel an invoice.
With this fix, a warning message prompts the user for confirmation before cancelling the invoice.
C067695 (MARma54616) Customer Order Management
Prior to this fix, right-clicking the Order-by Trading Partner field in the Order summary pane caused the MORE button menu options to appear.
With this fix, right-clicking the Order-by Trading Partner displays a context menu from which you may choose to view or edit the order-by trading partner (or create a new trading partner).
C061896 (MARma52798) Customer Order Management
Prior to this fix, the unit of measure (UM) conversion factor was always used to convert the delivery quantity to the weight and volume UMs.
With this fix, Protean uses the following logic to calculate the weight and volume of a delivery:
Protean checks for direct matches between the weight/volume UM and the user UM, primary UM, and alternate UM (in that sequence). If a direct match is found, then the appropriate quantity is copied to the weight/volume. If no direct match is found, Protean first tries to convert the quantity in the user UM to the weight/volume. If no conversion exists, Protean then tries to convert the quantity in the primary UM to the weight/volume, and finally if no conversion exists Protean tries to convert the quantity in the alternate UM.
The same logic applies to the invoice when Protean calculates the invoiced weight and volume.
(MARma53005) Customer Order Management
Prior to this fix, the unit of measure (UM) conversion factor was always used to convert the delivery quantity to the base UMs.
With this fix, Protean uses the following logic to calculate the base quantity of a delivery:
Protean checks for direct matches between the base UM and the user UM, primary UM, and alternate UM (in that sequence). If a direct match is found, then the appropriate quantity is copied to the base quantity. If no direct match is found, Protean first tries to convert the quantity in the user UM to the base quantity. If no conversion exists, Protean then tries to convert the quantity in the primary UM to the base quantity, and finally if no conversion exists Protean tries to convert the quantity in the alternate UM.
The same logic applies to the invoice when Protean calculates the invoiced and ordered base quantity.
C068862 (MARma55123) Customer Order Management
Prior to this fix, when a user copied or created an order from a standard order, if the order being copied was suspended or if it had lines or deliveries that were suspended, the suspended status was not copied to the new order.
With this fix, the suspended state is now copied. Users can change the suspended status by unchecking the Suspend checkbox in the New Order dialog box.
C070646 (MARma55501) Customer Order Management
Prior to this fix, Protean crashed when creating an order that had an order-by or ship-to trading partner with comments in the Basic tab that were not used for Customer Order Management. Now, with this fix, only comments that are Customer Order Management-specific for the ship-to trading partner are copied to the delivery. The warning message that used to display (message number 1230023) while creating the order with the trading partner no longer displays.
C070473 (MARma55435) Customer Order Management
Prior to this fix, a warning message (message number 1140580) incorrectly displayed during order creation if the selected market profile had a summary condition and no charge was associated with that condition.
With this fix, this warning message, which refers to a prorated charge, no longer displays under these circumstances.
MS16960 (MARma27146) Customer Order Management
Prior to this fix, online help for hold codes was not displaying properly. With this fix, you can now search Protean online help for information about holds.
C072640 (MARma56225) Customer Order Management
Prior to this fix, in the Order notebook, Protean crashed if more than 5 characters were entered in the Reason For Return field in the Delivery pane.
With this fix, the number of characters you can enter in the Reason For Return field is limited to 5.
C067223 (MARma54618) Customer Order Management
Prior to this fix, the Order notebook's toolbar icons and menu items for navigating to inquiries were not enabled if the order was open in View-Only mode.
With this fix, menu items and toolbar icons are enabled for the inquiries for which the user has workspace security, even if the order is open in View-Only mode. The inquiries are:
1. Inventory Inquiry
2. Invoice Inquiry
3. Market Profile Inquiry
4. Expected Shipment Inquiry
5. Expected Receipt Inquiry
6. Reservation Inquiry
7. Available to Promise (ATP) Inquiry
C070903 (MARma55715) Customer Order Management
Prior to this fix, when completing a delivery on a transfer order, the user was not warned if the shipped and/or confirmed quantity was 0 (zero).
With this fix, a user-defined severity (UDS) message (which has a default severity of Error) alerts users who attempt to complete a delivery that has a shipped and/or confirmed quantity of 0. The number of the new message is 1140589, and the message reads: "The shipped and/or confirmed quantity is 0 for this transfer delivery. Completing the transfer order will put both the Expected Shipment and Expected Receipt into a completed status so no further shipping or receiving activities can be performed against this delivery."
If the user completes a delivery on a transfer order and the shipped and confirmed quantities are not equal, then message number 1140527 is generated: "The shipped and confirmed quantities do not match for this transfer delivery. Completing the transfer order will put both the Expected Shipment and Expected Receipt into a completed status so no further shipping or receiving activities can be performed against this delivery." This message is also a UDS message (with a default severity of Error) because it may be acceptable that the shipped and confirmed quantities on a transfer order delivery are different, for example due to weigh-scale issues.
C063757 (MARma53559) Customer Order Management
The Protean Pricing action server finds the price sheet whose assignments best match the details of a customer order delivery. When more than one price sheet matches those details, the Pricing action selects and uses the most recently-created of those matching price sheets.
Prior to this fix, Protean used the most-recently created of the multiple matching price sheets, but users were not made aware of this.
With this fix, when there are multiple matches, Protean still selects the newest one but it also issues the following user-defined severity (UDS) warning message (message number 1140595): "Multiple valid price sheets were found with the same assignment criteria. The price sheet with the latest create date was used."
C024569 (MARma44733) Customer Order Management
Prior to this fix, on order deliveries the Promised Ship Date and Requested Ship Date were both calculated to a past date when the Requested Delivery Date and Promised Delivery Dates were left at the default (current date) and the user entered a lead time for the shipping site on the order delivery.
With this fix, a user-defined severity (UDS) message displays when a user specifies a lead time without changing the Promised/Requested Delivery Date. The following message (message number 1140586) warns the user that "Based on the lead time, the promised ship date and/or requested ship date will be calculated to a past date on the order delivery". The default severity of this message is Informational, but you can change it to Warning or Error. If you do not want deliveries to have a promise ship date in the past, you should change the severity to Error. This will prompt users to manually change the requested delivery date, the promised delivery date, the promise ship date, and/or the lead time.
C062202 (MARma53147) Customer Order Management
Prior to this fix, the table coorderdeliv had two indices on its PricingTPObjectID column (PRTPINDEX and IDXPRCTP).
With this fix, the redundant IDXPRCTP index has been dropped.
C068862 (MARma55122) Customer Order Management
Prior to this fix, when an order was created from a standard order or by copying from a regular order, add-on information from the original order was not copied to the new order if the add-on was defined with an Association option of Allow On Specific.
With this fix, when an order is created from a standard order or by copying from a regular order, add-on information from the original order is copied to the new order regardless of whether the add-on's Association option is defined as Add To All or Allow On Specific.
C069736 (MARma55288) Customer Order Management
Prior to this fix, when the defaulted Commission Trading Partner or Percent fields on the Commissions tab of the Order Delivery were overridden following a change in the Ship-to Trading Partner field of the Order Delivery and the order was saved with these changes and later reopened, the user-entered values in the Commission Trading Partner and Percent fields disappeared and were re-defaulted from the market profile.
With this fix, when the defaulted Commission Trading Partner or Percent fields on the Commissions tab of the Order Delivery are overridden following a change in the Ship-to Trading Partner field of the Order Delivery and the order is saved with these changes and later reopened, the user-entered values of the Commission Trading Partner and Percent fields are retained.
C062721 (MARma53201) Resource Costing
Prior to this fix, the rpstrmresc table (which is populated when the results of a cost run are loaded on the extract database) did not have resource description columns for stream resources.
With this fix, the table now has two description columns (Desc1 and Desc2) that are populated when the results of a cost run are loaded on the extract database.
C066831 (MARma54457) Resource Costing
The buttons on the Accept Cost Run Results dialog box have been changed so that they are more user-friendly. The Start button starts the acceptance process, the Cancel button stops the process, and the Close button closes the dialog box.
C063269 (MARma53426) Event Automation
The DEP (delayed event processor) has been changed so that the createshipmemo action server can now create a shipping memo even if the shipping activity form has been deleted. Instead of retrieving information from the shipping activity form, the createshipmemo action server now retrieves the information it needs from the expected shipment transaction.
C036058 (MARma47306) Financials
Prior to this fix, when a Financial Binder or Deposit Slip was in a Complete or Approved status, you could not void a cash document from it.
Now, with this fix, you can void the cash document. Later, the Binder/Deposit Slip will be recorded again using the same settings as the original record action, but with the remaining cash documents that were not voided. If there are no other cash documents on the Financial Binder or Deposit Slip after the voiding action, then the Binder/Slip will be left in Incomplete status.
This feature is available only if the Binder/Slip is in a recorded state; the status can be either Complete or Approved. This feature is not available if the Binder/Slip is not in a recorded state.
C038247 (MARma47823) Financials
Prior to this fix, message number 1100048 was an Informational message and you could not change the severity level. Payment generation could not be stopped when a check number was skipped.
With this fix, this message is now a user-defined severity (UDS) message. You can modify the severity level to Error. If you change the severity level to Error, payment processing will stop when a check number is skipped so that you can take appropriate action before payment generation resumes.
C070194 (MARma55406) Financials
The Source Document notebook's Other tab has two new read-only fields display the user that approved the source document and the date the source document was approved. The same two fields have been added to the Journal Entry notebook's Other tab. The new fields are called User and Approval Date, and they are available for queries.
These fields are updated when the source document (or journal entry) is approved. If a user un-approves a journal entry (that is, changes the status to Complete or Incomplete), these fields are blanked out and they are updated when the journal entry is reapproved. (Source documents cannot be un-approved.)
C069666 (MARma55132) Financials
When applying a credit memo receivable to an invoice receivable for the complete amount before the discount due date, a discount adjust is created. Prior to this fix, when a discount adjust action was undone, an un-apply action from the credit memo was erroneously generated along with the undo discount adjust for the complete amount.
With this fix, the un-apply action is no longer generated when a discount adjust action is undone.
C066076 (MARma54943) Financials
Prior to this fix, the Discount Adjust action prototype defined on the Payment Terms object was used to perform the Automatic Discount Adjust action, even though a different Discount Adjust action prototype had been defined on the source document prototype that was used to create the source document.
With this fix, the action prototype defined on the source document prototype is given precedence over the settings on the Payment Terms object. However, if the source document has been created without a prototype or if the prototype used doesn't define the Discount Adjust action prototype, then the settings from the Payment Terms object are retained and used.
C069527 (MARma55061) Purchasing
With this fix, purchasing users' source document profiles default as follows for invoice payable, credit memo payables, and debit memo payables:
The source document's profile is the default specified for the user on the User notebook Financial Defaults 2 tab. If no default is specified for the user, then the source document's profile is the default defined on Protean System Tailoring's Purchasing tab.
C069576 (MARma55136) Purchasing
Prior to this fix, the vendor invoice number was not saved on the source document. With this fix, the vendor invoice number is saved in the source document's description 1 field.
C072677 (MARma56241) Purchasing
Protean online help for the Protean System Tailoring utility Purchasing tab's "Invoice Tolerance for PO Close" field has been reworded to: "Enter the acceptable percentage difference that is calculated by comparing the received quantity to the invoicable quantity so that the purchase order can be closed."
C065991 (MARma54725) Purchasing
Prior to this fix, on the purchase order there were no delivery dates in the configuration table for the purchase order deliveries. With this fix, the delivery dates can now be added to the configuration table for the purchase order deliveries.
(MARma53715) Purchasing
You can now drill back to purchasing invoices that have been posted, as long as the purchasing invoices you're drilling back to have not been archived.
C065987 (MARma54238) Purchasing
Prior to this fix, when an invoice line was deleted from a purchasing invoice, the Calculated Invoice Total field was not updated immediately, making it inconvenient for data entry.
With this fix, the Calculated Invoice Total field is now updated immediately once a purchasing invoice line has been deleted.
C065989 (MARma54240) Purchasing
When an add-on is entered on a purchase order or purchasing invoice and a value is required on the add-on, you must now enter a value for the add-on before you can save the purchase order or purchasing invoice.
C067861 (MARma54673) Purchasing
Prior to this fix, when overriding the tax amount on a purchasing invoice tax, if the user pressed the Delete key to clear the Tax Amount field prior to changing the data, the Tax would be removed because the Delete key was being interpreted as the user's attempt to remove the tax. With this fix, pressing the Delete key to clear the Tax Amount field does not remove the tax; instead, it clears the amount out of the field.
C071463 (MARma55822) Purchasing
Prior to this fix, you could not use the arrow keys to modify the date and time on the purchase order requested delivery date and time. With this fix, now you can.
C071929 (MARma56019) Purchasing
Prior to this fix, the default query Selected Non-Inventory Items did not display non-inventory items whose Buyer field was blanked out. With this fix, non-inventory items display regardless of the content of their Buyer field.
C067857 (MARma55033) Purchasing
When you save or validate a purchasing invoice and the calculated invoice total amount is a negative amount, the following user-defined severity (UDS) message (message number 22155) displays: "The Calculated Invoice Total amount is a negative amount. This will create a document with a receivable (not payable) amount".
The default value for this message is Informational, but you can change it to Warning, Error, or Non-display by using the Message Manager.
C070186 (MARma55335) Purchasing
Prior to this fix, there was no way to receive non-inventory items through automation.
With this fix, this is now possible. The following interfaces are now exposed to support the receipt of non-inventory items through automation.
1) CNonInventoryItemReceivingMgr
Properties: Purchase Order, Fiscal Date, NonInventoryItemReceipts
Functions: SetReceivedQtyEqualToExpectedQty, CompleteAllDeliveries, Update
2) IPROTEANNonInventoryItemReceipts
Properties: Count
Functions: Item
3) IPROTEANNonInventoryItemReceipt
Properties: ReceivedQuantity, CostCenter, CompleteDelivery
C063565 (MARma53483) Activity
Protean online help has been updated to explain how to use the automation API for the following activity methods:
1. BOOL IPROTEANScheduleActivityLine.GenerateUnits (CUnsignedInteger, CDouble, BOOL)
2. BOOL IPROTEANUserDefinedLine.GenerateUnits (CUnsignedInteger, CDouble, BOOL)
3. BOOL IPROTEANShippingActivityLine.GenerateUnits (CUnsignedInteger, CDouble, BOOL)
4. BOOL IPROTEANReceivingActivityLine.GenerateUnits (CUnsignedInteger, CDouble, BOOL)
C070943 (MARma55757) Activity
Prior to this fix, in shipping activity, some shipping corrections incorrectly defaulted additional inventory information from the specified location. This occurred only if the location had exactly one piece of inventory, and that inventory was for the same resource originally shipped but had additional unit or lot tracking information. In this case, the lot and unit information defaulted into the shipment correction, changing the inventory from what was originally shipped.
With this fix, shipping corrections default no additional inventory information beyond what is specified in the correction line item. This ensures that the inventory specified in the correction will always match the original shipment activity line, regardless of what inventory is in the specified location at the time of the correction.
C049479 (MARma50735) Activity
In any Activity Form dynamic cabinet, when a user selects the option to display forms for (ALL) sites, activity reporting forms for reporting sites outside of the user's authorized list display in the cabinet. This is because activity forms have no standard site scoping like other objects do, and because the reporting site is not the same as an object scoping site. As a result, if the reporting site is considered to be the site that controls this ability, users can see and open activity forms for sites for which they are not authorized.
With this release of Protean, you have the ability to override this functionality.
With the new cabinet site security feature, you can add site security behavior to almost any site associated with an object (such as reporting site). If you use the new query definition filter, the filter will not display objects for sites for which a user is not authorized. This functionality is in addition to existing scoping site, admin site, and instance-level security.
To use this new feature for a cabinet:
1. Define a new query that uses the Limit To Accessible Sites checkbox for the site filter.
2. Associate the new query with the cabinet, and identify the new query as the default for the cabinet.
3. To prevent users from circumventing your new security by choosing other queries in the cabinet, disassociate any queries that would allow them to do so from the cabinet.
C065992 (MARma54549) Inventory
Prior to this fix, in the Expected Shipment Inquiry and the Expected Receipt Inquiry, the supplier/customer ID was displayed, but not the supplier/customer name (description). With this fix, the customer name displays, too.
C059137 (MARma51974) Inventory
Prior to this fix, the graphical view in the Available to Promise (ATP) inquiry displayed large numeric values in exponential format. These numbers were not easy to read.
With this fix, the inquiry now displays large numeric values in the ATP graph in normal format. The displayed data also takes into account the precision of the unit of measure (UM).
C071597 (MARma55872) Planning
The following information was added to Protean online help for the Time Horizon attribute for the Schedule Pane of the Capacity Scheduling window and the Resource Scheduling window:
"Displays the time horizon you selected using View - QS Preferences. You can change the time horizon at any time. The absolute start and end points of the horizon are calculated as follows:
* If a Planning Run has been completed: - The horizon start is the Planning Run Current Date minus the Past Due Days from the Planning Run Profile. - The horizon end is the Planning Run Current Date plus the Scheduling Days from the Planning Run Profile.
* If a Planning Run has not been completed: - The horizon start is the Extract Date minus the Past Due Days from QS Preferences. - The horizon end is the Extract Date plus the Horizon Days from QS Preferences.
The values in QS Preferences are saved in Protean Manager. If no values have been saved yet, the 'factory' default is 28 horizon days and 7 past due days. Note: If a Planning Run is paused between levels, the horizon values come from QS Preferences, not the Planning Run Profile."
C069570 (MARma55299) Planning
Protean online help for the Extract Profile notebook Planning tab's Scheduling Resource Selection Lists attribute now states: "Extract only those schedules that use the scheduling resources on the chosen selection lists."
C068957 (MARma54959) Planning
If you are configured to use PRISM as a data source, all extracts to extract databases are Full extracts; you cannot do a Selective extract.
C068580 (MARma56075) Planning
Protean online help for the Independent Demand attribute on the Planning ATP Inquiry Criteria Basic Tab, page 2, has been reworded to include the following text:
"For expected shipments, the following rules apply:
If it is an exceptional order, it will always be included. If master schedule entries are selected, only exceptional orders will be shown. If forecast is selected, only orders that are not within the forecast horizon will be shown."