Custom state / system object naming

RPD is highly customizable and could fit in almost every use case. But certain aspects are static and can only be changed by modifying the backend. For example, I want to be able to name Document objects "print element" instead when I use RPD in a commercial printing environment. The same goes for certain job states that aren't clear/intuitive like "no matching device" which means that the print job is ready for scheduling if no automatic scheduling is chosen.