cancel
Showing results for 
Search instead for 
Did you mean: 

Output Document File Naming Convention

Output Document File Naming Convention

Output Document File Naming Convention

We need the ability to configure/customize the file naming convention of output documents generated.

For example: We have 5 different types of output documents that we generate of one work order. The current naming convention is not human friendly and these documents are used by Back-Office and are send to customers.

The latest ServiceMax Go iPhone app, this has been changed just a little bit. the Work Order Number now shows properly, however the string behind it representing the date and time format is still a row of long numbers. The SFM used is not in the name and it is not possible to see which of the 5 SFM's is used hence which type of output document it is and thus has to be viewed one by one.

FSA For Windows and generating a service report online shows a worse naming convention however the API name is also included. We have APEX Trigger code available online which renames the entire document to a proper name of the SFM Transaction and the Date Time format is also properly named.

For example:

Estimate Report WO-00226344 07-08-2019 13.58.35.pdf

Acknowledgment Report WO-00226344 07-08-2019 13.58.35.pdf

Service Report WO-00226344 07-08-2019 13.58.35.pdf

Service Report - With Price WO-00226344 07-08-2019 13.58.35.pdf

Instrument Acceptance Form WO-00226344 07-08-2019 13.58.35.pdf

 

On short term we need the SFM name back in the naming convention. In the long term we need to be able to configure this according to custom wishes. For example directly in the SFM transaction where have control of the entire naming convention so we can have the same details as demonstrated above which will apply to documents generated online, and in all apps 

What is the underlying problem do you intend to solve with this idea?
Clarity of the output documents so you an see what it is and also from which SFM
How is the problem being addressed today, if at all?
There is no solution then manually opening each generated document and manually renaming it
Product Area?
Output Documents and ServiceMax Go
What version of ServiceMax are you on?
19.2
Tags (1)
5 Comments
Grill Chef
Grill Chef

We face the same problem using the classic FSA Ipad app. We requested this also already but without success.

 

Sushi Chef
Sushi Chef

We are emailing output documents to a customer after customer signature and emailing works only when report name is in a certain format.

We also had to customize ServiceMax Go output document name to the same format which was used in old mobile / tablet apps so that emailing to customer would work.

Would be nice to have more friendly way to change output document names than Apex code.

 

Sushi Chef
Sushi Chef

fyi @laurim 

Fry Chef
Fry Chef

This is a must. The document name looks pretty bad and we even have customers asking if we can change how it's displayed. 

Fry Chef
Fry Chef

Hey Everyone,

I was able to update the naming convention with Flow. However, you can't completely change the pdf file name because the SVMX code depends on it, BUT you can add to it and still keep the OTB servicemax feature of sending the email after it's generated.  

Attached is some basic screenshots of how I did this.

The SFM checks a box on the work order after the report is generated. This is was triggers the process builder to rename the attachments with flow. You need to parse out everything to the left of ".pdf" and add what details you need in the middle. Now, while a long ugly PDF name is not desirable, this will still allow customers to better manage their reports. 

I hope this helps!

-Victor, the Fry Chef report_name_2.pngservice_report_name_flow_1.png