6.5.7

Folder URL's - When using the READ API and passing the parameter "documentid", if docuflow determines that document ID does not exist, it will then check if the id is a folder. If the id exists, the read functionality will assume that we are reading a folder and return a folder URL. If we were seeking a document and its corresponding document id existed, then the read API would function as before.

Auto applying cascade policy - In the even we want to enable cascade policy on a folder upon its creation we would add to the ini under [Box Connection]<insert-cms-name>.box.autoCascadePolicy=true. By default, this is set to false.

Content server search bypass - Traditionally when retrieving content via content server there are extra API calls due to how retrieval in box works utilizing content server metadata. In some scenarios we may instead limit the meta data utilized and instead retrieve the document via it's box document id. By not retrieving the document by its content server document id we reduce the number of API calls required. Inside SAP the BOX document id would be linked. Discretion is advised upon using this functionality as it is not meeting SAP specifications. To enable this performance feature in the active ini file under section [Content Server] add <insert-cs-name>.contentServer.searchBypass=YES to the corresponding content server connection.

Folder URL expiry time - When sharing box folder URL’s, we can set the expiry time. Default is 60 seconds. You can change the expiry time by modifying the active ini profile under section [Content Server] we can add the following rule<insert-cs-system-name>.box.boxURLFolderExpiryTime=360 (the following example would expire a shared folder URL after 10 minutes).

Real time search - Box released a new search API to retrieve items. However, that requires using a new query language. The advantage of using this new query language is we can avoid the previous 10-minute delay when documents are initially indexed using the previous API. Anywhere a traditional "mdfilter" (metadata filter) array was used it would be replaced with a new box search query. An example is given below, { "from":"enterprise_761921896.sdInvoice", //the enterprise id followed by the metadata template "query":"docuflowSaplinkEnabled = :value", //the field we are wanting to check "query_params":{ "value":"True" //the value of the item it would hold }, "ancestor_folder_id":"131865107848" //the folder where want to start looking } This is traditionally used in SAPLink, we would just modify the filter field in the sap link rule in the active ini file. To enable this functionality we would add <insert-cms-name>.box.searchQueryEnabled=true by modifying the active ini profile under section [Content Server]

Nested folder creation with file placement - A new tree structure folder creation. In the custom table, the first row holds the folder hierachy that is comma delimited. <folder1>,<folder2>,<folder3> where folder 1 and folder 2 belong to folder 1. To enable metadata creation along with the folder creation send along ZFOLDER_METAFLAG='X'. ~ indicates where file placement occurs In the return table expect to see a format similar to this, !<folder-name>,id (! is an identifier for parent when parsing) ~<folder-name>,id (~ is an identifier for children when parsing)

New web user interface to configure docuflow middleware - It can be accessed via https://localhost:82 (username: docuflow, password: docuflow) **Can be changed.

Kubernetes support