hi All, is it possible to directly change process variables in In process-

@eaglez Added to the above, I would like to add some more content as follows:

1. You may create a process which will capture the updates in the database or in the same process in the form of PVs. This process can be either made as a Related Action or you may invoke it using fn!startprocesswrite() at https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQeCToV_iK9c-uZFaHQndbxbAQOV2CNBg/view/summary in-case if you are looking forward to trigger the process via a SAIL component(such as button).
2. With regards to updates to PVs in the destination process, you may opt for one of the following:
a. Configure a 'Receive Message Event' in the destination process and upon receiving the message, the PVs should be updated by performing a database read operation or read values by querying process analytics (based on the process id that has sent message) or read the values from the message itself. This approach needs a 'Send Message' event configuration in the source(Related Action or the process model triggered using fn!startprocesswrite()).
b. Use 'Set External PVs' smart service at https://forum.appian.com/suite/tempo/records/type/components/item/i4BCLGOdlMUpdGVqT-RV7oRg74uEGJO7ST7vajpgHr5N88A8C7XkID6LIPzexYr/view/summary to make updates in the destination process by making use of the process id. The downside of this approach is that, the 'Set External PVs' might need to be reconfigured as and when there are changes in PVs. And as said earlier, this lacks audit history. This is more or less similar to what other practitioner has said.

@eaglez Added to the above, I would like to add some more content as follows:

1. You may create a process which will capture the updates in the database or in the same process in the form of PVs. This process can be either made as a Related Action or you may invoke it using fn!startprocesswrite() at https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQeCToV_iK9c-uZFaHQndbxbAQOV2CNBg/view/summary in-case if you are looking forward to trigger the process via a SAIL component(such as button).
2. With regards to updates to PVs in the destination process, you may opt for one of the following:
a. Configure a 'Receive Message Event' in the destination process and upon receiving the message, the PVs should be updated by performing a database read operation or read values by querying process analytics (based on the process id that has sent message) or read the values from the message itself. This approach needs a 'Send Message' event configuration in the source(Related Action or the process model triggered using fn!startprocesswrite()).
b. Use 'Set External PVs' smart service at https://forum.appian.com/suite/tempo/records/type/components/item/i4BCLGOdlMUpdGVqT-RV7oRg74uEGJO7ST7vajpgHr5N88A8C7XkID6LIPzexYr/view/summary to make updates in the destination process by making use of the process id. The downside of this approach is that, the 'Set External PVs' might need to be reconfigured as and when there are changes in PVs. And as said earlier, this lacks audit history. This is more or less similar to what other practitioner has said.