Wanted to see if I'm doing something incorrectly or if this is normal behaviour.
We use Griffin Auto+ plus to nest jobs based on a Job Id and number of files.
For example if a Job has a job id of Job50 and contains 50 individual files.
We then trigger on N number of files using a private data key.
We then use the Artwork properties Group identifier to group base on the Job50.
The expectation is that the Job50 with 50 files gets nested in Griffin.
Griffin Auto Issues
-
plutinolabs
- Newbie
- Posts: 13
- Joined: Sat May 13, 2023 2:07 pm
- Location: Melbourne
Re: Griffin Auto Issues
Hi jasonx
Take my advice with a grain of salt (i use phoenix, not griffin - but they work similarly.)
I think the group identifier doesn't split files into jobs, it groups files inside the job. For example, say if you have 50 files in Job50 and 50 files in Job51 all coming to the same folder in switch at the same time. You could have the situation where it would take 25 files from each job (since you requested to plan 50 files) then the nesting result would be grouped into 2 layouts of 25 of each inside the job (1 for each group identifier).
In Phoenix there are plan conditions that would segment based some condition (eg only look for files with a job id of Job50, then nest 50 of them) - but i'm not sure Griffin has that capability.
A work around that might work would be to combine all pdfs of a job into 1 document in switch and use the Multi-page file handling option in the griffin module to split them into products inside Griffin. This assumes all files have the same page handling (ie all double sided or single sided, all have the same qty). Then you could do a plan of 1 file with the job id - then you won't have any other files conflicting.
Take my advice with a grain of salt (i use phoenix, not griffin - but they work similarly.)
I think the group identifier doesn't split files into jobs, it groups files inside the job. For example, say if you have 50 files in Job50 and 50 files in Job51 all coming to the same folder in switch at the same time. You could have the situation where it would take 25 files from each job (since you requested to plan 50 files) then the nesting result would be grouped into 2 layouts of 25 of each inside the job (1 for each group identifier).
In Phoenix there are plan conditions that would segment based some condition (eg only look for files with a job id of Job50, then nest 50 of them) - but i'm not sure Griffin has that capability.
A work around that might work would be to combine all pdfs of a job into 1 document in switch and use the Multi-page file handling option in the griffin module to split them into products inside Griffin. This assumes all files have the same page handling (ie all double sided or single sided, all have the same qty). Then you could do a plan of 1 file with the job id - then you won't have any other files conflicting.
Re: Griffin Auto Issues
The older version had these trigger options. We've just moved to the newever version so now experiencing these new issues.
- Attachments
-
- Screenshot 2026-02-20 134104.png (52.06 KiB) Viewed 18 times
-
plutinolabs
- Newbie
- Posts: 13
- Joined: Sat May 13, 2023 2:07 pm
- Location: Melbourne
Re: Griffin Auto Issues
That looks like what's in phoenix. Looks like they may have missed that feature in the new app. Might have to put in a feature request.
Can you still use the old switch app with the updated Griffin? I assume the app is putting jobs through the griffin api, so the old app still might work. Unless you want to get a little crazy and make your own switch app for Griffin using the api
