nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

# Submissions Attribute

Sara Friebel

Description

In need of an attribute for # of Submissions by candidate regardless of filters in report for Taleo OBI.

Use Case and Business Need

In Taleo, we can only report on # applications/submissions based on the filters in our report. However, we'd like to be able to report on # of submissions at an attribute level (ideally both inactive and active) to see a full history of that candidate. We'd like to identify New Applicants vs. One and Done Applicants vs. Eager Appliers.

Original Idea Number: f2fe96b8d9

# Submissions Enhancement Request 2.28.18.png

Find more posts tagged with

Submitted

Agents

Analysis

BI Publisher

Status: Submitted

Comments

Michael Scaduto

Sara, you might be able to get to this using a SQL filter or filtering based on the results of another analysis.

Below is an example of a SQL filter where the filter is returning the Candidate ID of any submission that accepted an offer within a timeframe. The WHERE statement can be modified for a broader purpose than just offer accepted dates.

"Candidate Identification"."Candidate Identifier" in (
SELECT Q.Cid Cid
FROM
(SELECT "Candidate Identification"."Candidate Identifier" Cid
FROM "Recruiting"
WHERE
"Submission Dates"."Offer Accepted Date" BETWEEN @{start}{timestamp '2017-11-01 00:00:00'} AND @{end}{timestamp '2017-11-20 00:00:00'}) Q )

Filtering based on the results of another analysis is a similar in concept to the SQL filter... include Candidate ID in Analysis 1 with your report filters, then in Analysis 2 you would filter based on Candidate IDs identified in Analysis 1 (screen shot attached).

2-28-2018 9-41-20 AM.jpg

Sara Friebel

Hi Michael - Thank you for the suggestion! Unfortunately, the volume of applications we have is too high to run these results based on another analysis. Our applications run in the millions just for the previous year so the report times out/fails when we try to run on another analysis. I think for small scale adhoc reports this would work great. Thank you again!

Michael Scaduto

I've never tried a SQL filter to quite that volume but it will handle more than basing it on another analysis. I agree it would be beneficial if there was an easier way to execute this scenario with a larger data set.