TOTVS Fluig English

Árvore de páginas

Você está vendo a versão antiga da página. Ver a versão atual.

Comparar com o atual Ver Histórico da Página

« Anterior Versão 2 Próxima »

See below the new features available in the Fluig 1.4.9 update:


 

BPM

Display of platform activities

According to the business area, a workflow process must fulfill multiple requirements - validate user data, integrate data with the ERP, legacy systems, etc. - and what must be displayed to users while such requirements are processed by Fluig? This new version allows displaying a specific message based on the current Fluig action, as per the data entered in the form. For real. 

Interested?

 Check out the use details in Workflow Development

  

ECM

View document comments by the public API

 The “listDocument” and “listDocumentWithChildren” methods of the public API used to list documents are now even more complete. They now feature document comments – “additionalComments” attribute.

Do you want to know more?

 Go to the public API to check out the enhanced methods.

 

 

Fixes

 In this session, we have listed a few bugs we fixed in this update to make sure that everything runs smoothly on your platform.

  • Posting and view .jpeg images using the internal viewer.
  • Access to document browsing folders created from webservices.
  • Printing of controlled document copies attached to workflow processes.
  • Viewing the main request, under the My Requests area of the Task Central, when the process has subprocesses in parallel activities.
  • Visual monitoring of the process design to display requests whose flows have subprocesses in parallel activities.
  • Deletion of a workflow work group from user registrations.
  • Use of text formatting styles in the content editor.
  • Queries via datasets in text-type form fields with apostrophe.
  • Handling of requests when forms have more than one version.
  • Method of verifying and creating indexes in Oracle databases that affect the platform startup.
  • Search in standard and custom zooms after entering the contents to be considered and pressing Enter.  
  • Return of users after performing queries using a “colleague” dataset without considering internal platform users. 
  • Handling of requests with forms after entering duplicate data in a field that requires validation.
  • Security in importing and exporting processes, defining that only users with permission in the process settings page can perform such actions.
  • Handling of requests in mobile devices when the Parent x Child form data is stored in database tables.

  • Generation of BIRT reports that use service-instancing datasets.

    Note

     Learn more about how to develop BIRT reports in Report Development.

  • Presentation of an explanatory message when users wish to access private content – from the corresponding content link – of communities in which they do not participate.

  • Standardization in the return of inconsistencies occurred with the “publisherID” or “colleagueID” parameters of the “createFolder” method of the “ECMFolderService” webservice, when used in integrations.

    Note

     More information is available in Using Webservices.

 

 


  • Sem rótulos