https://netsuiteprofessionals.com logo
Join Slack
Powered by
Sorry for the cross-posting. Just really hoping so...
# advancedpdf
j
Sorry for the cross-posting. Just really hoping someone here might have a solution in their back pocket:
a
I'd imagine you cold create a workflow that removes whatever print button you want from the record, that uses a role-based condition. I know I've done this with print buttons on Estimate records and the like, so imagine it should be doable with Vendor Payments.
j
It's not the print button on the record I'm concerned about, it's the actual print queue at Transactions > Management > Print Checks and Forms (checks)
if it was a button on the record I'd be all over restricting that with a workflow
It's more like there's a particular page (https://xxxxxx.app.netsuite.com/app/accounting/print/printchecks.nl?printtype=transaction&trantype=check&method=print&title=Checks&whence=) that I need to prevent users from accessing.
open to any other ideas if you have them @al3xicon. You can't put a workflow/script on a non-record page, can you?
a
can't really think of a different idea - why does that user need to be able to view vendor payments, if they're not allowed to print checks?
j
reporting mostly. If they don't have access to that transaction record, won't saved searches and the like completely exclude those record types (i.e. won't tie to the financial statements)?
a
I guess - with saved searches you could try to run them unrestricted. But I'd be curious which financial reports require the vendor payment record type. It's mainly a cash transaction so I would think it wouldn't be involved in P&L or Balance Sheet reports. I guess if they're looking at cash reports then yeah it wouldn't be there
j
yeah, balance sheet would def include the bank accounts
a
but yeah you can't have a script deployed to the print checks page at all
😭 1
maybe like a greasemonkey script on their browser or something
or - this is real hacky - you could include logic in your template maybe when printing to not show anything if the user is in a given role
or something like that
I mean I guess it's odd to me that a user would need to view/print balance sheet reports but not be allowed to print checks - couldn't you just ask them not to? Seems like over security to me but IDK
j
ooh, that's a clever idea about the template!
but yeah, I think it's more about making sure no one's messing with the queue when they shouldn't be
agree that should just be able to ask ppl, but my controller is super exacting about controls
a
gotcha
another option might be building an exception report to catch when people do this who shouldn't
but the criteria would be tricky to get right
that is reactive though and the controller may not go for it
j
yeah that's my thinking
it's going to be a tough sell though
really smart idea to blank out/error out the check form that everyone else sees so at least they don't get a check form of any kind though. I had already restricted the "real" check form, but having a blank/error one will definitely help sell the detective control a bit.
e
You can also create a script to execute on a record's print mode. Another idea (long thread; may have been mentioned)
a
@ec interesting, this is something I haven't thought of really but could be a creative way to do this
3 Views
Open in Slack
PreviousNext
Powered by