In some cases, operations are shown multiple times, each with a unique number at the end of the name. The number indicates the version of the operation, with higher numbers indicating more recent versions. If there is no number, it is the original version of the operation. Services may have different versions as well.
As changes are made to the Replicon system, new versions of the services and operations may be created. By creating new versions instead of changing the existing ones, we can ensure your integrations are unaffected by compatibility issues caused by application changes.
For example, consider an integration that transfers projects from another system to Replicon. The integration was built using the PutProject operation. Later on, a required field is added to projects in Replicon. If the existing version of PutProject is updated with the new required parameter, the integration would immediately start to fail as it does not provide the required field. Instead, PutProject2 is created to support the new field. The original PutProject is updated so the required field does not have to be specified, perhaps by automatically setting it to a default value. Because the parameters for PutProject have not changed, the integration can continue to work as is.
When building new integrations, we recommend you use the latest versions of services and operations. For existing integrations, typically you can continue to use older versions as they will still be supported. However, the older versions may not allow you to take advantage of newer functionality.