Hy,
I'm currently updating my project from Camel 2 to 3.
I have created a custom component with different endpoints and consumers/producers.
In the documentation of these endpoints I use labels to group them:
#UriEndpoint(label = "ourServerProduct,delivery,upload,download")
#UriEndpoint(label = "ourServerProduct,administration,user")
Using "label" was deprecated in Camel 3 so I tried to migrate it to "category".
The problem here is that "category" is an Array of the enum Category, which has a lot of predefined values, but I need to use custom values as these endpoints are used to talk to our server product.
As enums can not be extended in java, how could I create custom categories using this new documentation type.
Thanks
Chris
You cannot do that, at this moment you have to choose on of the enums, or use the old deprecated label.
But it would be good to add Cateogory.CUSTOM. You are welcome to create a JIRA and provide a PR if you want as well.
Related
I am building a doc editor like google doc using react-slate for the frontend and express for the backend. It works well when one person types in the editor but I faced one problem when some people typed in one editor. When two people or some people type the content in one editor, we should merge all the states and show the acceptable result to all people.
How to implement the functionality? on the frontend or backend side?
I've seen a few questions somewhat related to this, but no clear answer. This documentation makes it appear that Salesforce Documents can be used to grab a document for signature: https://developers.docusign.com/salesforce/code-examples/salesforce-embedded-sending-signing#1-create-and-send-envelope
However, when looking at the Apex Toolkit, it seems you still need to use the template methods to get a template from DocuSign with the signature tags.
I would ideally like to get this template from Salesforce if possible. Can anyone confirm if this is possible or if it's required the template live in DocuSign proper.
If it CAN live in Salesforce, how would I go about adding the anchor tags for signature and date?
manual tab placement is not available in the Apex Toolkit, but the Apex Toolkit does support anchor tagging you can't supply positional data, but you can use anchor strings to auto-tag a doc on the way out
Background:
I just started researching on DocuSign a couple days back and was told by DocuSign Customer Support to post questions here on SO. I am running a trial version of DocuSign to evaluate the capabilities and see if it fits our needs. We are using Classic version of Salesforce.
Business Case:
We generate hundreds of documents that need to be sent to different signatories based on certain conditions and once the signatories receive the doc, they need to select a value from a custom tag (dropdown) on the doc which will then be passed back to Salesforce.
Thanks to answers posted on SO, I know how I can dynamically add recipients to a DocuSign doc and also how I can pass values from Custom Tags back to Salesforce.
However is it possible to dynamically prepopulate documents with one or more updateable custom fields or does it have to be manually dragged and dropped onto the document each time we send the doc over?
Any pointers/references to documentation would really be appreciated.
Referencing the API documentation (below), it does look like its possible to add dynamic tabs. There is limited information on wether they can be updated, but I would suggest you try something like POSTMAN or any other REST API client that you can test this on.
Presumably, you can create this on SalesForce if you're inclined. Otherwise, you'll need to use some sever-side language to send the request.
https://developers.docusign.com/esign-rest-api/guides/features/tabs
firstly, we have a custom profile with rules from different sources. We want to add some tags to these rules in order to classify them according to our requirements.
We are adding our tags directly into the database with SQL, in the table rule_metadata but the problem is that in the sonarqube interface our new tags works fine when we scan a project (the new tags works in the issues tab) but when we see the rules tab we can not filter the rules or find our tags.
Any idea of how can we add tags to the rules in this way and make the sonar interface works with them? we try restarting sonar, making new projects etc.
The database is not an API, you should never directly insert data in it.
You should use UI or Web service to interact with SonarQube.
As a consequence of updating the DB, there's no warranty of what can happen...
I'm building a large SaaS CRUD application using ReactJs. There is a classic navigation need for the whole application, something like the following pattern for every object:
Item list -> Item detail -> Item edit/delete
|------> Item create
For every type of object, you can list then or create a new one. In the listing, you can see details, edit or delete an item. The application will have a top navigation menu that you move you to the object type chosen listing.
In terms of Relay, every object type will hold its query. The detailsview will work with the query fragments.
Seems that a simple router would be enough, but I don't want to start using old stuff or deprecated code.
As far as I understood, Relay Modern cannot work with React Router V4, although I've seen questions regarding ways to use React Router V4 with Relay Modern. So:
a) Can I use RRV4 for that type of application ? Will I have a problem with that?
b) If not, should I go for RRV3 or Found ? Which one is recommended ?
You may consider found and found-relay. I am evaluating them now and appreciate that found explicitly addresses the problem of request waterfalls with static routes. Found Relay supports Relay Modern.
I don't see why RRV4 wouldn't work with Relay, take whichever router you prefer. RRV4 seems like a good choice.