客服电话
APP下载
迪恩网络APP
随时随地掌握行业动态
官方微信
扫描二维码
关注迪恩网络微信公众号
开源软件名称（OpenSource Name）：bullhorn/starter-kit-spring-maven开源软件地址(OpenSource Url)：https://github.com/bullhorn/starter-kit-spring-maven开源编程语言(OpenSource Language)：Java 98.9%开源软件介绍(OpenSource Introduction)：Bullhorn Starter Kit (Spring/Maven)The Bullhorn Starter Kit is a collection of Java code that lets you integrate custom business logic with the Bullhorn CRM application. The code itself is 100% boilerplate and should require no modification, but rather is designed for plugging in your own classes or extending existing ones. The following technologies are required: Run The application uses Spring Framework extensively, but Maven handles all dependencies. These are some other useful links around Bullhorn APIs:
There are several ways to customize Bullhorn through this repository, including:
There are also several other ways to customize Bullhorn, but that are specific to the older UI/UX called 'S-Release'. This functionality within the starter-kit-spring-maven is considered deprecated, and is subject to be removed with future releases:
The Starter Kit includes code for dealing with most of these methods of customization. Each of these is discussed below. One of the main concepts used for form triggers, REST triggers, and subscription-based scheduled tasks is the workflow, which is described first. WorkflowsThe concept of a workflow is based around the idea of implementing large amounts of custom business logic while maintaining readability and encapsulation. The starter-kit's design for workflows has recently changed; this documentation describes the newer framework. Workflows are no longer stored in separate XML files, but instead are entirely configured via JAVA code, as is common in more modern JAVA/Spring applications. The general idea is to add Spring beans to the starter-kit's Application Context, and they will automatically be inserted into the correct workflow. This is done by extending standard abstract classes and annotating them with @Service
public class ValidateSalary extends PlacementFormTriggerValidator {
@Override
public void validate(PlacementFormTriggerTraverser traverser) {
//business logic
}
}By extending one of these classes, you are forced to implement an abstract method specific to the kind of workflow you're adding to (for REST Triggers and Form Triggers the method is TraversersThe various implementations of Traverser perform two main duties, providing an easy way to retrieve all information related to the entity being passed through the workflow, and maintaining state throughout the workflow. The Traverser object is the only thing any given Of the two main types of Traversers, there will be an implementation for each entity that is valid for that type of Traverser, and similar implementations for the corresponding helper (i.e. there are TriggerTraversers for each entity that can have a Form Trigger or Rest Trigger applied to it, and ScheduledTasksTraversers for each entity that supports subscriptions). The entity-specific implementations provide not only the entity being passed through the workflow, but also methods for retrieving each of the main associated entities. For Form Triggers there are methods to retrieve the form data itself, an instance of the entity the form represents populated with that form data, as well as the currently persisted entity. For example, on a PlacementFormTriggerTraverser's helper, you can expect methods like the following: public Placement getNewEntity();
public Placement getOldEntity();
public FormPlacementDto getFormValues();
public Candidate getCandidate();
public Job getJob();
public List<PlacemenCommission> getCommissions();
...REST TriggersREST Triggers are similar to form triggers in that they allow you to customize how a record gets saved, but from various different places in the application as opposed to just on the standard edit/add pages for an entity. Specifically, a REST Trigger gets called whenever a consumer of the REST API makes an add or update call and passes a URL parameter
The Starter Kit handles all REST Triggers in the same way...the controllers all live in
To implement custom logic, you extends one of the ${entityName}RestTriggerTraverserThe rest trigger implementations of The REST Trigger-specific helper classes are considerably different than their form trigger counterparts, mainly due to the kind of request we receive from BULLHORN when a REST trigger is called. Essentially when a REST trigger is called we only receive the fields that are being modified at that time, so for instance if a user edited status on a JobOrder from the list, and we had a REST trigger configured, we would receive a package roughly like {
"status": "Submitted"
}The helper objects handle this in two ways. First, when Subscription-based scheduled tasksSubscription events are one of the most powerful concepts available with the Bullhorn APIs. The starter-kit implementation of them handles the API calls the standard way, described below, and then passes each event returned by those calls through the scheduled tasks workflow for the entity for which we received an event. The first step in creating a subscription-based task is to subscribe to the types of events you want to consume. The easiest way to do this is by using SOAPUI along with the SOAP documentation. You essentially load the WSDL into SOAP UI and then make a Once you have successfully created a subscription you should have a name for it which you provided in the Having completed these steps, you are now ready to run your app and consume Bullhorn events. Every time the Cron Expression we provided triggers, our application will ping Bullhorn asking for any new events for the subscription we created. If it finds any, it will loop over them, sending each one through it's appropriate scheduled tasks workflow on a different thread. All scheduled tasks are defined by extending the various Below are some details about the particular implementations of ${entityName}ScheduledTasksTraverserThe implementations of Most of the functionality provided by the ScheduledTasksTraversers and associated helpers is relatively straightforward and includes utility method for finding other REST entities, checking if a particular field was updated on the event being processed, and retrieving the API Event object itself. One particular piece of functionality of note deals with saving entities on events via the Bullhorn APIs. We provide a method public <T extends UpdateEntity> T getOneEntityToSave(T entity);That should be used to perform updates on entities in a scheduled tasks workflow. You pass in the entity you are about to make modifications to, which the helper object then makes a deep copy of using Kryo and holds onto in a Map, returning the deep copy. Then, at the end of every scheduled tasks workflow, the code that executes each of your Date Last Modified-based scheduled tasksIn some cases it may make more sense to write a scheduled task that operates off of a Bullhorn record's In order to write such a task, you would create a class (typically in
Finally you will need to implement the method to execute your business logic. This method is called The framework itself runs every minute by default (controlled by the Form triggers (deprecated, S-Release only)Form triggers are a way for you to customize how a record is saved in the Bullhorn CRM. For each of the main entities, there is both an 'add' form trigger and an 'edit' form trigger. During the configuration of a given trigger, you provide a URL to Bullhorn that is called upon saving the form. Bullhorn passes all information on the form to the URL in the form of an HTTP POST request. The code receiving the request can reply in one of two ways, either stopping the save with a provided error message, or modifying the data that is about to be saved. The following form triggers are available for customization:
The Starter Kit handles all form triggers in the same way. The endpoint controllers are all in the
To implement custom logic, you must extend one of the various ${entityName}FormTriggerTraverserThe form trigger implementations of In order to add an error to the traverser.addFormResponse("error:clientCorporationStatus", "Client Corporation cannot be saved in this status");Note that each key provided to the response must be unique, since we use a In order to add a return value to the traverser.addFormResponse("returnvalue:status", "Approved");Will respond to Bullhorn telling it to set the status field to a value of 'Approved' before saving the entity. Form Scripts (functionality removed)The functionality supporting Form Scripts in the starter-kit-spring-maven has been removed. To view or obtain the old documentation or functionality, view an older commit/release of the starter-kit. Custom tabs (starter-kit-spring-maven functionality deprecated, use the extension-starter)In Bullhorn, Custom Tabs are what they sound like...they allow you to add custom content onto a tab of any of the main types of entities. Configuration typically only consists of providing a URL endpoint that you wish to be iframed in the aforementioned tab, and consequently this allows for essentially any type of customization. An additional parameter with the name
Due to the extremely large variety of possibilities with custom tabs, there is very little generic/boilerplate code in the starter-kit for them. However, one of the most common requirements is for a relatively simple to-many entity...essentially a table on a custom tab that acts as a UI for data attached to the main entity. Typically the data for this table is stored in a cloud MySQL database, then when we hit the tab we query for the records specific to the one we're on using the passed EntityID parameter. Database TablesTo configure a cloud MySQL table, we use Hibernate and JPA, both provided by Maven. Spring has some nice integration which we utilize, an example of which lives in @Entity
@Table(name = "EXAMPLETABLENAME")
public class JpaExampleEntity extends AbstractJpaEntity<Integer> {
private Integer id;
private Date date;
private String email;
private String text;
private BigDecimal number;
private Integer digits;
private String creditCard;
private String url;
private String password;
private String selectValue;
private Integer yesNo;
public JpaExampleEntity() {
super();
}
public JpaExampleEntity(Date date, String email, String text, BigDecimal number, Integer digits, String creditCard,
String url, String password, String selectValue, Integer yesNo) {
super();
this.date = date;
this.email = email;
this.text = text;
this.number = number;
this.digits = digits;
this.creditCard = creditCard;
this.url = url;
this.password = password;
this.selectValue = selectValue;
this.yesNo = yesNo;
}
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(name = "id")
@Override
public Integer getId() {
return id;
}
@Override
public void setId(Integer id) {
this.id = id;
}
@Column(name = "date")
public Date getDate() {
return date;
}
public void setDate(Date date) {
this.date = date;
}
@Column(name = "EMAIL")
public String getEmail() {
return email;
}
public void setEmail(String email) {
this.email = email;
}
@Column(name = "text")
public String getText() {
return text;
}
public void setText(String text) {
this.text = text;
}
@Column(name = "number")
public BigDecimal getNumber() {
return number;
}
public void setNumber(BigDecimal number) {
this.number = number;
}
@Column(name = "digits")
public Integer getDigits() {
return digits;
}
public void setDigits(Integer digits) {
this.digits = digits;
}
@Column(name = "creditcard")
public String getCreditCard() {
return creditCard;
}
public void setCreditCard(String creditCard) {
this.creditCard = creditCard;
}
@Column(name = "url")
public String getUrl() {
return url;
}
public void setUrl(String url) {
this.url = url;
}
@Column(name = "password")
public String getPassword() {
return password;
}
public void setPassword(String password) {
this.password = password;
}
@Column(name = "selectValue")
public String getSelectValue() {
return selectValue;
}
public void setSelectValue(String selectValue) {
this.selectValue = selectValue;
}
@Column(name = "yesNo")
public Integer getYesNo() {
return yesNo;
}
public void setYesNo(Integer yesNo) {
this.yesNo = yesNo;
}
...
}jQuery datatables frameworkAfter the database configuration, we have a table, an object representing it, and an object to perform database actions on the table using our object. Assuming we want a relatively simple to-many entity, we can utilize the jQuery DataTables back-end and front-end framework present in the starter-kit. The javadocs provide detailed information about the different extension points, but the general idea is we extend Custom overview components (deprecated, S-Release only)Custom overview components allow us to customize the overview page of one of the main Bullhorn entities. Similar to Custom Tabs, configuration involves providing a URL which gets iframed on the overview. See the SOAP documentation for some more information. Again similar to Custom Tabs, Bullhorn provides some context information in the form of URL parameters appended to the base URL for the component. They include
Custom components are available on the following entities:
Custom edit components (deprecated, S-Release only)Custom Edit Components are again relatively similar to both Custom Tabs and Custom Components...Bullhorn allows us to provide an iframe URL which essentially acts as the Edit Type for a particular field (only certain fields can be used with Edit Components, the general rule-of-thumb is any customXXXXN field can be used). Additionally, we can provide a height and a width in pixels that Bullhorn will use when creating the iframe. The URL will be iframed on the edit tab for the entity which we configure it for, and we can pass a message to the edit tab from the iframe telling Bullhorn what value we want to set the field to. The following function function getQueryStringParameter(href, paramName){
var regexS = "[\\?&]"+ paramName +"=([^&#]*)";
var regex = new RegExp( regexS );
|
2023-10-27
2022-08-15
2022-08-17
2022-09-23
2022-08-13
六六分期app的软件客服如何联系？不知道吗？加qq群【895510560】即可！标题：六六分期
今天小编告诉大家如何处理win10系统火狐flash插件总是崩溃的问题，可能很多用户都不知
今天小编告诉大家如何对win10系统删除桌面回收站图标进行设置，可能很多用户都不知道
今天小编告诉大家如何对win10系统电脑设置节能降温的设置方法，想必大家都遇到过需要
我们在使用xp系统的过程中,经常需要对xp系统无线网络安装向导设置进行设置，可能很多
今天小编告诉大家如何处理win7系统玩cf老是与主机连接不稳定的问题，可能很多用户都不
电脑对日常生活的重要性小编就不多说了，可是一旦碰到win7系统设置cf烟雾头的问题，很
我们在日常使用电脑的时候，有的小伙伴们可能在打开应用的时候会遇见提示应用程序无法
今天小编告诉大家如何对win7系统打开vcf文件进行设置，可能很多用户都不知道怎么对win
今天小编告诉大家如何对win10系统s4开启USB调试模式进行设置，可能很多用户都不知道怎
请发表评论