index workflow status

[Bruno CAPELETO]

Dear Roberto,

I discovered Mayan yesterday and after installation it is looking so promissing that I am already spending my 2nd night on it :-)

Looking through the Q&A I understood the concept behind the Indexes (I was first looking at automatic folders).
However, I could not find how to build advanced indexes regarding workflow.

As an example of workflow, let's take a bill workflow with the following status : in preparation / issued / paid
What would be the syntax of the index to retrieve the bills separated within the 3 different status ?

More generally, where could one find the different possible syntaxes ?

Thanks in advance,
Bruno

[Roberto Rosario]

Hi Bruno,

Thank you! We have worked very hard.

At the moment while not documented it is possible to index documents based on their workflows properties. This is not finished yet (which is why is not documented) and after transitioning the document from to a new state, that change will not be reflected on the index. 

This is the syntax to access the current state of a document's workflow.

{{ document.workflows.all.0.get_current_state }}

 "all.0" gets the first workflow instance for the document. Ways to access a document's workflows by their label or a slug (instead of an id) are being explored.

A big refactor of the workflow system is planned post version 2.1. 

https://gitlab.com/mayan-edms/mayan-edms/wikis/roadmap

Hopefully we'll have time to add workflow indexing support as part of the overhaul. 

[Bruno CAPELETO]

Hi Roberto,

It works as expected with :

{{ document.workflows.all.0.get_current_state }}

But I do not manage it with the following :
{{ document.workflows.all.0.get_current_state=EN_PREPARATION }}

Any idea ?

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/s8fGI-5BN6k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mayan-edms+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aniket Mohapatra]

Hi Bruno,

Could you please explain me how you achieved this. I have a requirement in which I need to show the current status of the flow along side the document so that the users can know if the document was approved or rejected.

Regards,

Aniket

[Bruno CAPELETO]

Dear Aniket,

At that time I did not understand the concept well.

Actually I am still using the syntax "{{ document.workflows.all.0.get_current_state }}" which lists all the different possibilities and classifies the documents within a tree.

I still can not see the current state of a document during its visualization.

Cheers,

Bruno

To unsubscribe from this group and all its topics, send an email to mayan-edms+unsubscribe@googlegroups.com.

[Roberto Rosario]

Version 2.2 beta 1 has the improvement of showing documents filtered by workflow and current workflow state. Please give this beta a try to see if this is what you were aiming for.

[Cédric MARCOUX]

Hello, i'm trying to do the same, indexes based on Worflow state.

Still any solutions?

Thanks for your help

[Aniket Mohapatra]

Hey,

Sorry, I didn't find a solution to it.

Regards,

Aniket

--

[Roberto Rosario]

The new version 2.2 added a menu item that allow looking up documents explicitly by their workflow state.

[Clemens Hupka]

Hi!

Am Montag, 1. Mai 2017 01:09:44 UTC+2 schrieb Roberto Rosario:

The new version 2.2 added a menu item that allow looking up documents explicitly by their workflow state.

This works for me, except for the documents that are in the initial state. This view stays always empty... 

On Thursday, April 27, 2017 at 3:31:09 PM UTC-4, Aniket Mohapatra wrote:

Hey,

Sorry, I didn't find a solution to it.

Regards,

Aniket

On 27-Apr-2017 8:13 PM, "Cédric MARCOUX" <cedric....@cmbc.be> wrote:

Hello, i'm trying to do the same, indexes based on Worflow state.

Still any solutions?

Thanks for your help

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/s8fGI-5BN6k/unsubscribe.

To unsubscribe from this group and all its topics, send an email to mayan-edms+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Regards,

Clemens Hupka. 

[Roberto Rosario]

Hi Clemens Hupka,

just noticed what you experienced and could be the way initial state is defined (without making an actual transition from "None" to the initial state). Fixing this will need some changes in the way initial states are tracked or create an initial state detection for the menu entries for the edge case of initial states.

[Bruno CAPELETO]

Dear Roberto,

At last I could find the time to upgrade and I saw your new menu, sorry for the (very) late answer.

No, that is not what I was aiming at ; actually I achieved it via the index menu as I stated previously, and with more flexibility (I could subdivide based on a metadata value).

My remaining issue is when working/visualizing a document : the workflow state is not visible without going into the workflow menu. Same for the metadata (which is very critical for the efficiency).

There are still things to improve in the user interface so that it becomes usable in an efficient way, which I have to admit is not the case yet.

Bruno

[Bruno CAPELETO]

Dear Aniket,

Did you try  {{document.workflows.all.0.get_current_state}} ???

For me, that made the job !

Le jeudi 27 avril 2017 21:31:09 UTC+2, Aniket Mohapatra a écrit :

Hey,

Sorry, I didn't find a solution to it.

Regards,

Aniket

On 27-Apr-2017 8:13 PM, "Cédric MARCOUX" <cedric....@cmbc.be> wrote:

Hello, i'm trying to do the same, indexes based on Worflow state.

Still any solutions?

Thanks for your help

--

---
You received this message because you are subscribed to a topic in the Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mayan-edms/s8fGI-5BN6k/unsubscribe.

To unsubscribe from this group and all its topics, send an email to mayan-edms+...@googlegroups.com.

[Roberto Rosario]

Testing an experimental code to trigger index rebuild on workflow changes and other document associations like tags. 

So it could be possible to reference workflow state in a reliable manner in indexes in the next version.

Workflow rendering is in my personal wishlist, still in the process of testing Python diagram drawing libraries before committing to one.

[Bruno CAPELETO]

Dear Roberto,

The workflow system as such works fine - even if a bit cumbersome. So I would weigh that UI part as priority close to 0, especially in comparison to the assignation of metadata.

At which place can I describe exactly my wish of what should be done regarding that ?

Bruno Capeleto, Dirigeant 5 rue de la Potasse / 68850 STAFFELFELDEN Tél. 03 69 61 60 20 / fax 03 69 61 60 29 http://www.abcreseau.com Lauréat Concours Alsace Innovation 2010

To unsubscribe from this group and all its topics, send an email to mayan-edms+unsubscribe@googlegroups.com.

[Roberto Rosario]

Hi Bruno,

Here in the list is good. Once the details are polished a ticket can be added in the code repository.

On Wednesday, May 24, 2017 at 5:08:35 AM UTC-4, Bruno CAPELETO wrote:

Dear Roberto,

The workflow system as such works fine - even if a bit cumbersome. So I would weigh that UI part as priority close to 0, especially in comparison to the assignation of metadata.

At which place can I describe exactly my wish of what should be done regarding that ?

Bruno Capeleto, Dirigeant 5 rue de la Potasse / 68850 STAFFELFELDEN Tél. 03 69 61 60 20 / fax 03 69 61 60 29 http://www.abcreseau.com Lauréat Concours Alsace Innovation 2010