Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Patch Name:       AdeptiaSuite_6_8_11Aug14Aug_2017.zip

Build Tag:           Release  Release_6_8_11Aug_2017

This is the incremental patch and can only be applied on the following Build TagTags: 

  • Release_6_8_10July_2017
  • Release_6_8_00_01_12July_2017
  • Release_6_7_12June_2017

What's New in this Release?

  • Support to Improve Traceability for a Company to for Companies to Trace and View Partner Specific Resources
    You Companies can now trace and view the following resources specific to a Partner:
  • Support to Re-run Post Process Transactions
    Adeptia Connect now allows you to re-run the aborted post process transactionsPost Process Transactions.

  • Support to Create EDIFACT Inbound/Outbound Template
    You can now create inbound/outbound /wiki/spaces/AC2/pages/655640//wiki/spaces/AC2/pages/655660 Template for EDIFACT using an EDI template type. You can also view the execution details of the EDIFACT Inbound and Outbound Transactions from the Dashboard screen.

  • Support to Promote Objects
    You can now change the details of the Transactions and Templates at the target environment during migration by using the Promote feature. This is available in Migration utility, click here to know more.

  • Support to View Partner Specific Variables
    Now you can define the additional parameters for the Partners while creating a an /wiki/spaces/AC2/pages/659860//wiki/spaces/AC2/pages/659187 Template.

  • Support for Mapping Functions
    With new mapper functions /wiki/spaces/AC2/pages/656554 added in the Data Mapper, you can now map the fields of the source and target applications.

  • Support to Copy Xpath of Mapping Field
    You can now use the xpath of a mapping field in other functions. You can achieve this by copying the xpath /wiki/spaces/AC2/pages/656554.

  • New Triggers and Actions
    New triggers and actions are available in BambooHR and Shopify application applications.

  • Support to change the File-based application in an Inbound Template
    You can now change the file-based target application while editing an Inbound Template.

Bug Fixes

  • In the Firefox , the label of Update Picture is not displayed properly browser, when you update the image of a company or a profile, the label of Update Picture is not displayed properly.
  • When you activate While activating a transaction with File as a source application, then in the Dashboard -> Trigger section, "Last Execution status" is does not get updated .Source and Target in the Dashboard -> Trigger section.
  • While creating a Template using a business app, then the source and target fields are invisible at the source on the Mapping screen when you create a Template using a business app on the source side.  On the mapping screen.
  • While creating a Template or Transaction, on the Encryption and Decryption screens, you are not able user is unable to search the key manager while creating a Template or Transaction
  • When you execute While executing an EDI Outbound transaction, then following errors occurred in the Dashboard -> Triggers section,
    • N/A is displayed in the
    previous run and next run columns and also status and last execution status columns are displayed as blank
    • Previous Run and Next Run columns, and 
    • Blank status is displayed in the Status and Last Execution Status columns.
  • Pre-Process Template is not exported while exporting Post Process Template using transaction. 
  • When you deploy a user deploys Post Process template with published process flow then at the target environment, the process flow is displayed in an unpublished statestate at the target environment.
  • Unable to edit the accounts, layouts, and mappings if they these are used in the Template or Transaction.
  • While executing a process flow with large file size (1.5 GB) then Java heap space error occurs.
  • While downloading large file size from FTP server, a high memory consumption error occurs.

See also

Patch Deployment Guide