Hi,
JobBase is for scheduled job which supports stop. TO make it appears in admin UI, you need this attribute:
[ScheduledPlugIn(
DisplayName = "Incremental Search Index Job",
Description = "This job indexs incrementally",
LanguagePath = "/Commerce/scheduledjobs/incrementalsearchindexjob")]
Regards.
/Q
Hi Quan,
The class does have it, which is why I am stumped. Below is the attribute used:
[ScheduledPlugIn(
DisplayName = "[HubSpot] Blog Import",
DefaultEnabled = false,
InitialTime = "1.1:0:0",
IntervalLength = 1,
SortIndex = 0,
IntervalType = ScheduledIntervalType.Days)]
public class ImportJob : JobBase
{
........
-Brad
Is there a chance that your scheduled job is disabled?
Can you try with this:
DECLARE @JobID INT
SELECT @JobID = pkID FROM dbo.tblPlugIn
AND TypeName = '<your-job-class-type-with-namespace'
IF @JobID IS NOT NULL
EXECUTE netPlugInSave @PlugInID = @JobID, @Enabled = 1
GO
/Q
Hi, adding my 2 cents here too as I had the similiar "issue".
As we can see in Brads code he has the "DefaultEnabled=false" => the job is not enabled. I had this set too but on purpose as I assumed it would be mapped to the admin UI Active property of a job but as it turns out it actually is mapped to the job enabled property which means that when false it will not be displayed in scheduled jobs listing.
I think the easier and supported way of fixing the enabled or not in the Admin UI is to go to the Config tab in Admin mode -> Plug-in manager (under the tool settings) -> From the Plug-Ins list find your assembly that has the job and click it -> Switch to the overview tab -> Check the enabled checkbox for the job and hit Save.
Or you can use this guy: http://nuget.episerver.com/en/OtherPages/Package/?packageId=TechFellow.ScheduledJobOverview :) Should enlist all jobs, even those that never have been started or registered as disabled (scheduled plugin instance not saved.)
Anyone have an issue where a class deriving from JobBase doesn't appear in the UI? The class is in a referenced DLL from another project. The strange part is that is shows locally for me, but not on the remote dev server which has a different database.
I have a current work around that creates a new class deriving JobBase and just calls the execute function of the job that doesn't appear in the UI which works, but I would rather not have to keep the wrapper.
Thanks,
Brad