[GH-ISSUE #177] Allow multiple automates to add tags on single file #139

Open
opened 2026-02-25 21:31:17 +03:00 by kerem · 3 comments
Owner

Originally created by @croontje on GitHub (Oct 16, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/177

Originally assigned to: @ciur on GitHub.

Right now if there is an automation that matches the file it gets executed. So if I have an automation that searches for "Invoice" and that adds the tag "Invoice" the file gets moved and the matching stops.

But imagine I have 3 kinds of documents: "Invoice", "Contract", "other"
And 20 companies

For each of those kinds of documents I have to make automations for all the companies: 20*3 = 60
But if you make it possible to have multiple automations to match a single file you can make an automation to tag the document types, and one fr each companyname: 20+3=23

And imagine it would be possible to have an automation that tags a file with the year: 2020, 2021, ...
You can add a single extra automation and tag each of the files with an "year" tag.

(of course only 1 automation can move a file)

Originally created by @croontje on GitHub (Oct 16, 2020). Original GitHub issue: https://github.com/ciur/papermerge/issues/177 Originally assigned to: @ciur on GitHub. Right now if there is an automation that matches the file it gets executed. So if I have an automation that searches for "Invoice" and that adds the tag "Invoice" the file gets moved and the matching stops. But imagine I have 3 kinds of documents: "Invoice", "Contract", "other" And 20 companies For each of those kinds of documents I have to make automations for all the companies: 20*3 = 60 But if you make it possible to have multiple automations to match a single file you can make an automation to tag the document types, and one fr each companyname: 20+3=23 And imagine it would be possible to have an automation that tags a file with the year: 2020, 2021, ... You can add a single extra automation and tag each of the files with an "year" tag. (of course only 1 automation can move a file)
Author
Owner

@dani commented on GitHub (Oct 18, 2020):

Yes, this would be a great enhancement ! Destination folder could be optional for automates, new documents would flow through all the automates until one which has a destination folder set is met. Ordering automates would be needed though.

<!-- gh-comment-id:711135304 --> @dani commented on GitHub (Oct 18, 2020): Yes, this would be a great enhancement ! Destination folder could be optional for automates, new documents would flow through all the automates until one which has a destination folder set is met. Ordering automates would be needed though.
Author
Owner

@amo13 commented on GitHub (Nov 13, 2020):

As of now, I think this is semi-possible already. I can confirm that the documents which I drop into the inbox match multiple automations and get the respective distinct tags. The only thing is that I can't say beforehand where they will be moved if the automations instruct to move the document to different placed.

Tied to #196

<!-- gh-comment-id:727075541 --> @amo13 commented on GitHub (Nov 13, 2020): As of now, I think this is semi-possible already. I can confirm that the documents which I drop into the inbox match multiple automations and get the respective distinct tags. The only thing is that I can't say beforehand where they will be moved if the automations instruct to move the document to different placed. Tied to #196
Author
Owner

@ajarzyn commented on GitHub (Nov 28, 2021):

As @dani mentioned "Ordering automates would be needed though."

In my opinion that would be best solution to prioritize automation easily making linked list from them.
+1 on priority on automation from me.

Maybe it would be better to open "Feature request" for this functionality alone?

<!-- gh-comment-id:980824104 --> @ajarzyn commented on GitHub (Nov 28, 2021): As @dani mentioned "Ordering automates would be needed though." In my opinion that would be best solution to prioritize automation easily making linked list from them. +1 on priority on automation from me. Maybe it would be better to open "Feature request" for this functionality alone?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/papermerge#139
No description provided.