[Feature request]: Integrate assets description field in the PDF

[apvlv]

Contact Details

No response

Is your feature request related to a problem? Please describe?

Hello shelf.nu!

You are evolving from day to day greatly, thats fantastic. Still, some users want more flexibility when handling bookings. Currently there are some features missing like quantities of items (if i have 50 camera batteries, i don't have a proper way to keep it organized, if someone wants to rent only 7 etc. apart from creating a long list of the same items).

What I really miss though is a possibility to fill in the existing feature gaps with some basic modifications to the system

Describe the solution you'd like

I would like to have more flexibility to customize the booking process with description and custom fields. If I have an asset which I currently not want to be a kit because of how kits are working now, I would simply put a description to the asset of which parts it is composed, like a video projector has a remote, a power cable, manual, etc.

Yes, it is possible to save a description along with the asset, but it's not very useful that there is no possibility to show this description on the generated PDF. So I would like to see an option before generating pdf to include the description, or better select which (custom) fields should be integrated into it. I think it would be a nice addition which isn't too feature specific at this stage of development.

Thank you! :)

Describe alternatives you've considered

No response

Additional context

No response

[carlosvirreira]

Hi @apvlv i like some of the ideas shared here. Thank you very much.

[carlosvirreira]

hi @apvlv we have another issue in which we will print the booking description to the pdf.

currently looking into designing another ui for the pdf.

[apvlv]

That's great, thanks Carlos! 👍

[carlosvirreira]

Quick visual of allowing to toggle on asset descriptions on a booking export. For sure custom fields will be a pain to visualize. This could work. Thoughts @apvlv ?

[DonKoko]

@carlosvirreira another idea. We discussed configuring columns but if we go for this layout you are suggesting, theoretically we can instead allow the user configure the "Extra content" per asset and just list everything below. So yes for some assets it can get very long but if the user has the freedom to choose what to show that shouldn't be an issue. Then we can allow them to add any custom field value or the description or basically anything we choose to.

[apvlv]

@carlosvirreira @DonKoko I like the idea with the extra content best, as an item could retain the description field for it's original purpose :)

[carlosvirreira]

@DonKoko @apvlv

I am all for freedom and dont mind designing. I just do not see anyone having a lot of joy having to toggle on things per asset for a large booking. Perhaps I am overseeing some detail. Maybe some idea might come up in the design process. Let's see what comes out.

[apvlv]

oh sorry, think I misunderstood @DonKoko. I thought the extra content is just a "custom field" belonging to each asset at the inventory layer, which can turned on to display in the pdf. But it's already possible to create custom fields :) just not to print them. Personally I accept any solution which gives the possibility to display extra information on the pdf.

[DonKoko]

Hey @apvlv & @carlosvirreira . I really didn't explain it well. Let me explain again:

1. When clicking "Generate PDF" you are presented with a selection screen
2. The screen says something like: "You can display some extra information for each asset in your list." This should come with a warning that you should be careful to not add too much content
3. The screen also shows a UI that allows you to select which fields to show. This is not per asset, this is for the whole document being exported for all assets inside it. Of course if asset A doesnt have a value for field X, it will be skipped when displaying it.

Once you select the fields and confirm, the PDF will be generated. The values of the selected fields will show in this manner, in 2 columns: left column is field name, right column is field value.

[carlosvirreira]

+1 for this