Printable form on acceptance of equipment

[paulo1624]

Expected Behavior (or desired behavior if a feature request)

Hi Snipe-IT, May I request to have this kind of printable form on acceptance of equipment. And also can i suggest to have a specific or choices to assign user to be print on this Tab "Print All Assigned.

---

Actual Behavior

(what actually happens goes here)

---

Please confirm you have done the following before posting your bug report:

• I have enabled debug mode
• I have read checked the Common Issues page

---

Provide answers to these questions:

• Is this a fresh install or an upgrade?
• Version of Snipe-IT you're running
• Version of PHP you're running
• Version of MySQL/MariaDB you're running
• What OS and web server you're running Snipe-IT on
• What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
• WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
• What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error
• If a stacktrace is provided in the error, include that too.
• Any errors that appear in your browser's error console.
• Confirm whether the error is reproducible on the demo: https://snipeitapp.com/demo.
• Include any additional information you can find in app/storage/logs and your webserver's logs.
• Include what you've done so far in the installation, and if you got any error messages along the way.
• Indicate whether or not you've manually edited any data directly in the database

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

https://snipe-it.readme.io/docs/getting-help

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[paulo1624]

hi snipeit any update or progress on this request? i hope this features will be included to your next new updates. this will be very help for us. Thank you

[wilsonlspacheco]

+1 (hosted costumer)

[snipe]

And also can i suggest to have a specific or choices to assign user to be print on this Tab "Print All Assigned.

I'm not sure what this means. Can you explain?

[paulo1624]

Hi snipeit any update on this request? thank You

[kagashe]

+1!

[paulo1624]

Any update on this ? Thank You

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

[stale]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[snipe]

Question for those interested in this feature:

What does this workflow look like, exactly?

• A user is sent the email for acceptance
• They sign the on-screen acceptance
• Then a printable form is available?

or:

• A user is sent not sent the email for acceptance but the asset is marked as pending acceptance
• The admin then prints out a form, has the user sign it, and then it's marked as accepted?

I'm interested in potentially getting this into v5, but I really need to understand exactly how folks see this working.

[EarlRamirez]

It would be nice to have this flow

• a user is sent an acceptance (pending)
• user digitally sign and the status is changed from pending to accepted
• signed form can be printed.

Not to certain if it will be good to have the location updated after the user sign the acceptance. Think the location can remain as is during checkout.

[Jhamende]

In my opinion It would be better to have the choices on checkout or a default action to be set in settings:

• Send an acceptance to the user (pending) OR generate/print acceptance form on checkout.
• user digitally sign and the status is changed from pending to accepted OR user sign physically the form and we change the status manually.
• Keep a copy of the signed form under user's documents.

[skiff2002]

@snipe, the second option, you proposed would be great.
@Jhamende, The way you proposed is exactly what I would like to see in this system.
I hope this functionality will be added in the next release.

[paulo1624]

Hi any update on this? thanks

[snipe]

@paulo1624 when there are updates to this feature, we will let you know by way of this ticket.

[AlfonsoQ]

@EarlRamirez i like this flow.
In addition, if the printed form is automatically attached to the asset, it would be more useful than the signature.

[jackka]

hello all.
Unfortunatelly, I can not wait until you release a solution and I start to developing it on my own.
further some thoughts about workflow with hope to feedback.
Workflow that you proposed is fine.
What do you think about this dual workflow with a paper and with a digital acceptance that both must be dependent each other?
By expirience of our company a paper process is prevail and users can skip the digital acceptance if they have a chance.
That is why our hard copy should to have place only after the digital acceptance has done.
Snipe, together developing is my aim.

[tymik]

totally +1, we'd need this!

[lorito-q]

We're also looking for this feature. I hope this will be in the next release!

[absqueued]

@snipe If this feature is not assigned to any dev and is in todo list - I would like to contribute.

[vorsoth100]

+1 This would be really useful for my company.

[berilslv]

keeping this up! This would be awesome solution! +1

[spbdimka]

+1 Need for Russian laws

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[jackka]

yes yes we still need it

[stale]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[ISNWAdmin]

Really looking forward to this feature as it could also address another slight deficiency. Currently, with only a signature stored, if the agreement text is updated, there's no way to show what text the user agreed to exactly.
Modifying the proposed workflow from above with added step:

• a user is sent an acceptance (pending)
• user digitally sign and the status is changed from pending to accepted
• signed form is generated (a pdf document with the signature inserted?) and added as a file to user documents
• signed form can be printed

Or the Agreement text could be stored with versioning history. Signed documents could be generated on-demand by pulling the version of the agreement text that matches the signing date and inserting the signature (and the check-out comments, optional?).

Either of the above would huge steps towards making the agreement/signature process actually useful. Currently, it's really just symbolic and wouldn't hold up to much scrutiny.

[seanlawson932]

I agree this would be very useful and helpful. It would be great to have a printable form, as well as one the EULA is 'Submitted' The admin email on file, is submitted the form in an email. It would also be cool to see that form show up in the files tab under the specific asset automatically. The sooner the better! Thank you! Great application I love all the features, this is honestly my only request that I would like/need to see. Thanks for all your hard work!

[zach78954]

I would love this, and honestly the only thing thats preventing me from switching to this..

[CartCaved]

This is essential functionality for my organisation. We need to have a physical signature before being allowed to hand over any equipment. So the second workflow from @snipe on 27 Jul 2018 is what would be needed for us.

* A user is sent not sent the email for acceptance but the asset is marked as pending acceptance
* The admin then prints out a form, has the user sign it, and then it's marked as accepted?

Essentially the workflow we need is this:

• A need arises for a user to have one or more pieces of equipment (a request inside or outside system)
• The device(s) are assigned by an equipment operator (admin) to the user.
• Optionally an email is sent to the user informing them that there are devices pending
• A form is generated
• The equipment operator and user meet, the user signs the form and receives the devices
• The equipment operator checks off the device acceptance
• Optionally the scanned signed form is saved with the acceptance
• Optionally an email is sent to the user with a notification that the devices have been accepted

I wasn't able to see any API hooks that could be used for plugging in to the acceptance workflow so it seems it has to be in the code, is that right?

[CartCaved]

Hi!

I'm not sure I understand the PR #10737 fully, but if it would be possible to upload a signed and scanned (or an electronically signed PDF) EULA instead of storing an electronic version, I think that would solve part of this feature request for us. It would still be great if Snipe could generate the form and wait to assign the items until the signed document is stored in the database.

Also, just checking again as I still could not find any relevant API hooks - could you confirm that this is functionlity that has to be added to the code and cannot be added as an external plugin, right?

[kaeser49]

Hi there,
not much progress for 4 years of begging. We have some nice printable forms on our Excel solution. How can I convince Management to switch away from Excel when we do not have some options to create certain handouts like print a task request for a certain asset to prepare it for a new handout?
Where can I change the form, resp. where is it stored in on premise install on Ubuntu?

[zsmbrvr]

I generate an EULA form using PowerShell and Snipe-It API.
Would be great if I could do it straight from the website.

[CartCaved]

I generate an EULA form using PowerShell and Snipe-It API. Would be great if I could do it straight from the website.

Would you be able to share your PowerShell/API solution?

[snipe]

We save PDFs of the acceptance signature - not sure what a powershell script would do here?

[CartCaved]

We save PDFs of the acceptance signature - not sure what a powershell script would do here?

Maybe I'm mixing up issues - but this issue is about generating a PDF, waiting until it has been signed (externally to Snipe in accordance with any local or organizational requirements, probably on paper), and only assign the equipment when the signature has been confirmed. And possibly storing a (scanned) copy of the externally signed acceptance form. See for example my earlier response to your request for more information.

My question about PowerShell and API was in response to the other user mentioning they have a workaround and I was interested in how that works - but we are all of course still very keen on a solution within the system!

[biorez27]

+1
Our company would like to have this feature too.

[tomasisko12]

+1

[TechInterMezzo]

This is essential functionality for my organisation. We need to have a physical signature before being allowed to hand over any equipment. So the second workflow from @snipe on 27 Jul 2018 is what would be needed for us.

* A user is sent not sent the email for acceptance but the asset is marked as pending acceptance
* The admin then prints out a form, has the user sign it, and then it's marked as accepted?

This is exactly what we would need as well.

[makeasnek]

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Please do not use bountysource. Many devs have had trouble getting paid there. You can check out this lemmy community as an alternative https://lemmy.ml/c/bugbounties

For statements from devs who have been unable to cash out from bountysource see:
https://github.com/bountysource/core/issues

Bug Bounties - Lemmy

Does your OSS project have an issue that needs fixing? Post a bounty here! We do not vouch for any projects posting bounties here or their ability to pay, you are responsible for evaluating risks yourself. Rules: 0. Title must state bounty amount in USD, EUR, or BTC. Crypto bounties are allowed, just list rough USD/EUR/BTC equivalent amount as well. Crypto bounties must be paid out in a Top 20 market cap coin. 1. OSS projects only 2. Limit one post per month per project 3. Your bounty must state who it is open to. If open to all, it can be in the body, if restricted by country it must be in the title. 4. Nothing illegal or morally questionable 5. No links to bountysource due to their ongoing payment issues.

GitHub

Issues · bountysource/core

Bountysource is the funding platform for open-source software. - Issues · bountysource/core

[tomasisko12]

This is essential functionality for my organisation. We need to have a physical signature before being allowed to hand over any equipment. So the second workflow from @snipe on 27 Jul 2018 is what would be needed for us.

* A user is sent not sent the email for acceptance but the asset is marked as pending acceptance
* The admin then prints out a form, has the user sign it, and then it's marked as accepted?

This is exactly what we would need as well.

We need this! Please SnipeIT make it happen.

[snipe]

We haven't used bounty source (largely because it hasn't worked properly) in years.

[tomasisko12]

We haven't used bounty source (largely because it hasn't worked properly) in years.

Hello Snipe, is there any plan to implement printing of form for checkin and check out so we can have physical signature on those form? Our organization required that. Many of our user doesnt have email address.

[tomasisko12]

bump

[coach1988]

Hello there,

we're currently evaluating Snipe-IT and as IT department, we really like it and it does make things a lot easier, thank you so much for all the countless hours you must have poured into this while keeping it open and free.

To effectively integrate into our workflows, we do need to get HR on board, but they require a document that contains the accepted EULA and the signature, so we are facing two main issues here:

1. We can only get a signature, but not the text, the signature expresses approval for
2. It is impossible to keep track of the EULA "version" that was signed, in case it changes down the road

I have two ideas about how I would love to see those things overcome:

1. The reports could get extended with a field that contains a copy of the EULA that was in place at the time of signing
2. A PDF could get generated at the time the signature is saved online, which contains all the information (date, time, eula, recipient, hardware): Already mentioned above, but I would also like to mention that sending it via email instead of attaching it to the asset/user would be a viable solution.

The platform already sends out notifications when a user accepts an asset, to both parties involved - These would be perfect to get it out of the door without having to save a pile of PDF's all the time. Important contacts are involved in the processes via the notifications, so they can create processes for themselves to preserve the information if necessary, the IT gets them anyways (or can regenerate it if idea 1 could find its way into the product) and the recipient can decide on his own if he wants to keep it or not.

PS: Really, thank you for your work.

EDIT: Please, ignore that, this is all we needed: #11524 (comment) (you should consider showing this column by default)

[snipe]

Hi @coach1988 - Thanks very much for the kind words. It's always very nice to hear.

We already do store the signed EULA with signature as a PDF (via commit #10737), for the very reasons you mentioned (point in time proof of what EULA they signed in that moment). You can find these under user history with their signature and also a download link to the PDF itself.