Yes, what you are describing is a very common example of what our life sciences customers use Tulip for. It is solved by using Tulip tables as the common data for all the apps. In other words the Apps all work with a common set of tables that maintain a current state of materials and resources.
So if you have a table that is for example called “Materials” (or batch, lot, unit, etc.) where each row in the table represents a batch (or discrete unit of material) then all apps can load a material record and change values as it works thru the process. Every table in Tulip has an audit log and as you change values in each record (cell in the row) Tulip records the changes in the table audit log. At the same time the app can save contextual and relevant process data in the completion records using the
The Tulip “Record History” widget is then used in combination of other analytics graphs and charts to display and browse the complete history record of the Material. BTW this pattern can also be used for a Table called for Example “Equipment” which gives you a full equipment log - used for equipment logbooks. In the same way an “Events” table can have information about deviations and quality events which in turn gives you full quality tracking features like in a QMS.
Remember that signatures are captured in the App’s completion record and can also be viewed in the Record History.
Following this pattern you can have different apps for different operations with multiple users logging in and signing electronically and support quite a complex manufacturing operations. We have plenty of examples of this type of use and soon many examples will be available in the Library.
I would also suggest to read the following 2 support pages.