Hi,
Added you to the main repository at GitLab. The main branches: Master,
Development, series/1.0 and series/2.0 are protected to avoid publishing
errors, but can create new feature branches for specific features/work as
needed. The branch layout follows a simplified model based on Git Flow:
Sorry about that. The code was just a test using the Python shell. I've
updated the app code
(https://gitlab.com/mayan-edms/document_renaming/commit/b09bf4a8dadf381cd8b54cb5f452119db8173a4f)
and now sequences can be created automatically with a rename template like
this:
{% set username =
The bug in the app was fixed, if no new bugs are discovered release 2 will
happen in a few days.
On Tuesday, January 12, 2016 at 4:45:58 AM UTC-4, Roberto Rosario wrote:
>
> Document stubs are just a blank entry in the database until the upload
> finishes. This gives you at least an ID that you
Here is a snippet to get you started:
https://gitlab.com/mayan-edms/mayan-edms/snippets/13221
- On a production deployed install, create a folder named 'scripts' and
put this snippet inside it.
- Add your access control list (role, document type, permissions) to the
line:
Hi,
Sadly there is nothing right now to automatically set a metadata value
after the document is uploaded or renamed. A custom app would need to be
created for this that would allow to define a macro or script.
On Friday, January 8, 2016 at 5:04:46 PM UTC-4, Rachael Sewell wrote:
>
> Hi
Document stubs are just a blank entry in the database until the upload
finishes. This gives you at least an ID that you can use via the API to
assign tab, metadata, etc until the backend finishes. By the behavior you
mention this appears to be a bug in the app. Thanks for reporting this.
Issue
Did a quick test and with Jinja2 it is possible:
from jinja2 import Template
from document_renaming.models import Sequence
document=Document.objects.first()
Template('{% set user = document.target_actions.first().actor %}{{user}}-{{
Sequence.objects.get(slug=user).next_value()
Hi,
The reason is being able to "see" local git commits inside the VM. The
provision script uses the synchronized git directory when deploying
(https://gitlab.com/mayan-edms/mayan-edms/blob/master/contrib/scripts/install/development.sh#L24).
If you select a branch and do a commit on the host,
Thanks very much. That's the direction I was going.
On Tuesday, January 12, 2016 at 3:20:04 AM UTC-5, Roberto Rosario wrote:
>
> Hi, thanks for trying out Mayan EDMS.
>
> Because any given document can be of only 1 document type, you would need
> to add the department name as part of the
I've had a few failed attempts at getting to the data through the Django
ORM. I'd like to get at the ACLs model so I can create a bunch of document
types (via a script) with varying roles and identical permissions lists.
Is the ORM a reasonable way to do this?
--
---
You received this
10 matches
Mail list logo
