Updated to 26R1

[zachary-doroshenko-veeva]

What was changed

• Adjusted README.md to contain updated links to the new developer portal.
• Updated pom.xml to newest stable release.
• Reworked VsdkProductServiceImpl.java and VsdkCustomNotificationServiceImpl.java to avoid deprecated methods.
• Updated Vault-Java-SDK-Common-Services-Sample.vpk with new code.

How this was verified

Scope: two deprecated APIs replaced; all other behavior unchanged. Goal
was to confirm the trigger -> action -> async job -> notification flow
behaves identically on 26.1.0.

Environment: Veeva Vault sandbox on SDK 26.1.0. Built with mvn clean compile, deployed via the Vault Java SDK Maven Plugin / project VPK, and
confirmed the SDK source shows valid/deployed under Admin > Configuration

Vault Java SDK. Required objects, fields, job definition, record
actions, document type and notification template were in place. Debug
logging enabled throughout.

Functional verification:

• Record Action "VSDK Create Product Application": ran the user action on
  a vsdk_product__c record and entered country__c; a new
  vsdk_product_application__c was created with product__c, country__c and
  product_type__c copied from the Product. Log showed "Number of Product
  records: N".
• Bulk Action "Create Product Application Documents": for each selected
  product application, a "VSDK Product Application Form" document on
  "General Lifecycle" was created with product__c and
  product_application__c set.
• Record Trigger fan-out to async job (PRIMARY Job-API regression):
  updating product_type__c on a Product (AFTER_UPDATE) enqueued
  vsdk_product_application_update_job__c via the new JobQueue API; the job
  ran (Job Status) and each related product application's product_type__c
  matched the parent's new value. Log showed "Querying product
  applications for parent ids", "Querying products for product types",
  "Setting Job Items", "Updating VSDK Product Application records".
• Job failure notification (PRIMARY Notification-API regression): forced a
  task to fail; completeWithError sent the
  vsdk_product_application_failure__c notification to the initiating user
  (RequestContext.getInitiatingUserId()) with tokens (failed_tasks,
  number_of_tasks, product_applications) populated. Log showed "Some Job
  Tasks have failed. Sending failure notification".

Deprecation-replacement regression (must behave identically):

• Async job enqueue (VsdkProductServiceImpl): JobService.newJobParameters
  • setValue + run -> newJobQueueParametersBuilder().appendParameter(...)
    -> newJobQueueRequestBuilder().withJobName(...).withJobQueueParameters
    (...).build() -> jobService.jobQueueOperation(request).execute().
    Verified the "product_applications" parameter is still received in
    VsdkProductApplicationUpdateJob.init() and the same records are updated;
    job name string unchanged.
• Notification recipients (VsdkCustomNotificationServiceImpl):
  setRecipientsByUserIds(Set) -> setRecipientsByUsers(List). Verified the
  same user(s) receive the failure notification as before.

Debug log reviewed across all cases — expected lines present, no
unexpected errors, and no RollbackException("QUERY_FAILURE" /
"OPERATION_NOT_ALLOWED") on the happy paths.